Re: How to control autogenerated custom dependencies ?
Sorry to quote the entire article, but I couldn't think of a good way
to trim it.
Anyway, what I would do is create a variable file for each of the
front-ends, so that only those will be loaded by custom (and will be
much cheaper).
The custom-load should then look like this:
(custom-add-loads 'eudc '("eudc-bbdb-vars" "eudc-ldap-vars"
"eudc-ph-vars" "eudc"))
Of course, don't forget to require the "var" files in their respective
"real" files.
-- Colin
Oscar Figueiredo writes:
EUDC consists of eudc.el for the front-end and eudc-ph, eudc-ldap and
eudc-bbdb
for the three supported backends. I would like the system to load only the
front-end and the necessary backend files according to the protocols the user
actually wants to use. The problem is I use custom and made eudc-ph, eudc-ldap
and eudc-bbdb be subgroups of the larger custom group eudc. Therefore
the generated custom-load file includes:
(custom-add-loads 'eudc '("eudc-bbdb"
"eudc-ldap" "eudc-ph" "eudc"))
which means that whenever I load eudc all the backends are loaded. I
really
need to avoid this.
What should I do ?
Oscar