| Summary: | emacs-cvs and new slots (wrong info-dir and stale symlinks) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Väth <martin> |
| Component: | New packages | Assignee: | Emacs project <emacs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | InOverlay |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | Emacs Overlay | ||
| Package list: | Runtime testing required: | --- | |
Hi, these issues have already been addressed in the Emacs overlay. Ad 1) Info dir: is now rebuilt in pkg_postinst. The INFOPATH (i.e. the env.d file) is controlled by an eselect module. Ad 2) The symlinks should be handled by the new eselect module, too. In general, SLOTting has also been reconsidered. There will be only one slot for each Emacs major version. So we will close this bug once the ebuilds from the overlay will be transferred to Portage. This will likely be in about two weeks when I have finished my exams and am back from a short trip. Martin, go and try the Emacs overlay, report any problems by bugzilla or email. Thanks, I was not aware about the emacs overlay. Indeed, it solves all issues, and the new slotting scheme has my vote. :) Please add also KEYWORDS='~amd64' to emacs-cvs and its new dependencies eselect-emacs and emacs-desktop when you transfer it to the tree - so far, it works great here on all of my 64 and 32 bit systems. (In reply to comment #3) > Thanks, I was not aware about the emacs overlay. Indeed, it solves all issues, > and the new slotting scheme has my vote. :) It has some advantages. > Please add also KEYWORDS='~amd64' to emacs-cvs and its new dependencies > eselect-emacs and emacs-desktop when you transfer it to the tree - so far, it > works great here on all of my 64 and 32 bit systems. This must be done by the architecture teams, I try to get access to a remote amd64 system and keyword it then. Fixed in 22.0.98, 22.0.9999-r10, and 23.0.0-r6, thanks for reporting. (Keywording for ~amd64 will follow soon.) |
Whenever a new emacs-cvs slot appears, I run into two troubles which I fix manually but which perhaps might be fixed in the ebuild: 1. At the first install the /usr/share/info/emacs-${NEWSLOT} is not treated correctly by portage (e.g. */dir is bzipped). The reason is that at the first install the new /usr/share/info/emacs-${NEWSLOT} is not yet contained in the INFOPATH environment variable when the new ebuild is installed. My workaround currently is to create an appropriate /etc/env.d/50emacs-cvs-${NEWSLOT} manually (and to call env-update to fix INFOPATH) *before* emerging the new slot, but this is obviously hackish. Maybe a solution would be to export an appropriate INFOPATH within the ebuild (although I haven't tried whether portage accepts such a "late" change of the environment in this case - if not, this might need to be a feature request for portage). 2. When deleting the old slot in advance, there are a lot of warnings about stale symlinks not being deleted. I do not understand the reason for this: The symlinks are dead because they pointed to the just deleted emacs; so why leave the rubbish on the disk? (Even if the user plans to install a new slot immediately afterwards, he has to clean up manually if he wants to be sure to have a "clean" disk, because the new slot might perhaps use less/different symlinks.)