Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: emacs-muse https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=181404 ------- Additional Comments From tagoh@xxxxxxxxxx 2006-04-24 23:13 EST ------- If we use the same things what Debian does, we don't rely on the trigger at all, which may mess up ;) For the reference, http://www.debian.org/doc/packaging-manuals/debian-emacs-policy especially see section 6. emacsen-common provides a facility to do byte-compile for every flavor of emacsen. What the elisp packages needs to do is, just to call emacs-package-install/emacs-package-remove in %post/%postun. and emacs-install/emacs-remove is for emacsen itself and to byte-compile all elisp available on system. it's useful when additional emacsen is installed on system and noone needs to install another package to use on it nor noone even needs to build another subpackage for that. So I don't think any packages need to do %ghost. packagers just needs to prepare the install/remove script and put it under /usr/lib/emacsen-common/packages/{install,remove}/, also just include all necessary elisp packages in rpm. that's it. you will miss the feature that queries the byte-compiled elisp files to rpm to know which package owns it though, I don't think it's an issue. For the compatibility, you can just exclude the incompatible flavor of emacsen in install script. Debian packages ordinarily does it as needed. HTH -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
