Re: Remaining package issues in latest (pre8) XEmacs

greg(a)alphatech.com wrote: > >>>>> "Darryl" == Darryl Okahata <darrylo(a)sr.hp.com&gt; writes: > Darryl> > Darryl> I've been buried in work and haven't had the time to hack on the > Darryl> code, but is there some magical variable that quietly suppresses the > PGP > Darryl> checks if PGP, etc. doesn't exist? > > No, it will just ask you if you want to continue without verification. OK, I'll whack together a patch for this. > Darryl> This brings up another question: should package-get always check > Darryl> for a locally-cached version and use that if it exists, instead of > Darryl> always downloading a package? I'd like to see this, but I don't know > if > Darryl> this would cause problems for others, and I'd prefer not having > Darryl> yet-another-config variable if I can avoid it. > > You can customize package-get-base-filename to something local, then > M-x package-get-update-base and type the path to ftp.xemacs.org when > you want that one. There's not a function to save the database, > though it is on my relatively short list. Whoa. The `package-get-base-filename' needs to be made into a plain filename (no directory, unless it's a relative path), that's located via the paths in `package-get-remote'. Right now, we've got two places that contains ftp site information, and we should be using only one (`package-get-remote'). Why make people change two variables when one will suffice? (This does, however, raise the problem where the `package-get-base-filename' file could be obtained from a different location from the other packages.) [ This is an hot issue for me, as I want to be able to stuff XEmacs plus all packages onto a CDROM for my friends and co-workers, and I took special pains to insure that changing a single variable (`package-get-remote') was sufficient to allow installations from CDROM (or other local disks). ] I'll be hacking on XEmacs soon. Should I fix this, or would you like to? -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.