Kevin Oberman <oberman(a)es.net> writes:
Is there a way of declaring the dependencies required by some
package
or must it be trial and error?
There was someone working on a dependency analyzer some time ago and
got it mostly working, but then it completely dropped out of sight.
Some specifics: ps-print.el seems to be missing.
A caveat: the roadmap files were generated by hand before everything
got packaged. package-get-base.el is very much more your friend now.
It's not in any roadmap file.
It's in the `os-utils' package.
Likewise term.el seems MIA.
term.el is in the eterm package (description = "Terminal emulation.").
And Gnus calls sort-subr which is not found.
sort.el is in xemacs-base. xemacs-base is pretty much required for
normal usage.
The jka-compr package also seems to be missing.
jka-compr.el is in `os-utils'.
I suspect that I'll eventually find all of them, but there needs
to be
a better way of helping the user through this!
Agreed.
On the other hand, tpu-edt seems happy in 21.0 once you get all of
the
packages it calls. I have only a single bug to track down so far.
You should get ownership/update access to the tpu package in the CVS
tree.