Pete Ware <ware(a)cis.ohio-state.edu&gt; wrote: Why include the version? The version information is already stored elsewhere, and there should never be a case when multiple versions are installed simultaneously (well, it could happen today, but it shouldn't be happening). When installing a new version of a package, the old package should be deleted. The visual package installer tries to delete the old version, if one exists, but it currently only deletes the lisp subdirectory (as there's no manifest file to tell it what else to delete). Yes, this is nice, but doesn't work for manual package installations. I thought about doing this for the visual package installer, but I didn't know where to store the information. You also need to take into account system vs user package installation locations (something which isn't done today), when installing packages (and manifest lists). It's a simple matter to modify the package-get routines to automatically keep track of a MANIFEST file (even on PCs), and use it to delete old packages. However, as already stated, this doesn't work for manual package installations. Hmm. What if we used a MANIFEST file, if one exists in the package distribution, but automatically create one if one isn't included? I'll whack something together and post it for comments. -- 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.

Valdis.Kletnieks(a)vt.edu wrote: You're confused with my use of the word, "install". I was referring to "installed within a running XEmacs", whereas you're talking about "installed on disk". Yes, you as a user should be able to install a different copy of "warthog" -- one that overrides any other, system-installed one. Let me clarify: There's no need to include the package version as part of the "pkginfo" database, as this information is already stored elsewhere (in each package itself, whereever it may be -- in the system or user area). Within each running XEmacs, it makes no sense to load multiple versions of a package, as this won't work for the vast majority of packages, and so there should never be a case where multiple versions are loaded into XEmacs simultaneously. You can have multiple versions stored on disk, but you can only load/use one of them. When installing a new version of a package, any old version, stored in the *SAME* place where the new one will be installed, should be deleted. This means that, if the user is installing a new package in his private package directory, any old version should be deleted from his private package directory, but any version in the system directory should not be touched (and vice-versa). -- 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.