In the current cvs cus-load.el has

    (put 'c 'custom-loads '("cc-vars" cmacexp cpp hideif "c"))

I think the "c" there is cedet/semantic/bovine/c.el.  I believe it won't
load under that name as the cedet subdirs aren't in the load-path.

That c.el file has

    generated-autoload-load-name: "semantic/bovine/c"

which I presume is designed for its autoloads.  I wonder if it should be
used for the custom loads too.  Seems a bit like hard work to remember
it in every sub-file, but building a load-path relative name might go
wrong in worse ways if making deps from files not yet in a loadable tree
or whatnot.

cus-load.el.subfiles.diff below is the what's changed by using
`generated-autoload-load-name'.  Notice for instance the "ede/locate"
one was previously loading "locate", which would mean the wrong
locate.el -- a danger of duplicate names among .el files I suppose.


2009-12-30  Kevin Ryde  <user42@zip.com.au>

	* cus-dep.el (custom-make-dependencies): Add hack-local-variables
	to pick up generated-autoload-load-name from
	cedet/semantic/bovine/c.el and similar.  This ensures
	"semantic/bovine/c" gets into custom-loads, instead of bare "c"
	which is no good as the bovine subdir is not in load-path.