Re: Some questions about packages
At 19:22 19/07/98 +0200, Olivier Galibert wrote:
I eventually played with package-* instead of untarring where
needed
and I think the low-level routines are quite nice. The only missing
thing is a point-and-drool interface for normal users[1] and a remote
This is partially provided by the customize interface on the menubar.
Some questions though:
1- I retrieve a package with package-get. How can I "activate" it ?
For instance, I find-file a Makefile. The editor yells at me that
makefile-mode is unknown (normal). I (package-get 'makefile). Now,
can I use it without restarting the editor ?
No. I have asked Michael to fix this but the change got postponed to
21.1/2. The problem is that the package paths are not rebuilt after you
install a package.
2- Is there a magical incantation to know why a given package
is
loaded by (package-get-update-all)?
I'd like to know why vm has suddendly[2] been considered necessary[3].
I thought this had been fixed. There is some discussion about dividing
"requires" into "really needed" and "needed for full
functionality"
3- If a package includes a dumped-lisp file and is retrived
after
having compiled and installed xemacs, will it work anyway?
No idea.
4- Is there another magical incantation to check for the
internal
consistency of the installed packages?
No
The question can be reformulated as "were installed packages
all
up-to-date, is there a function which says which packages
package-get-update-all would retrieve?".
No
andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp