On Wed, Jun 15, 2005 at 09:02:52AM -0500, Rob Browning wrote: > Joey Hess <[EMAIL PROTECTED]> writes: > > -- I need a way for a package's postinst script to check to see > > whether emacsen-common is configured and ready for > > /usr/lib/emacsen-common/emacs-package-install to run. The patch > > proposes checking for /var/lib/emacsen-common/installed-flavors, but > > it's not clear to me if this file is intended to be checked for by > > packages that use emacsen-common, or is purely internal and might be > > renamed tomorrow. Breaking all postinst scripts that use it. What > > should I do?
> Right now, there isn't any defined way to check whether or not > emacsen-common is installed. Current policy and emacsen-common > behavior has been set up to make sure that if an add-on package > depends on the relevant set of emacsen, then these emacsen will all > depend on emacsen-common, and the "right thing will happen" at package > install/removal time, and there won't be any race conditions. If we > want to make changes, we'll need to review/revise policy. > > I'm not opposed to that, but I'd like to be very careful. Back when > we devised the current policy, I wanted a more flexible arrangement > too, but the install-time details and corner cases really did > substantially constrain the set of correct solutions. Perhaps that > has changed since. I am aware that the original analysis was done a while ago, so is difficult to remember now the details, although many of the things there may still apply. But if you remember something about this kind of corner cases, it might help to improve the overall emacsen system. Regarding the original bug report and the proposed patch, I strongly agree with it and, even think that, even if the presence of /var/lib/emacsen-common/installed-flavors was not originally designed to check that emacsen-common is configured, that use seems reasonable and, unless problems become evident (like in specific corner cases that should be analysed) can be documented for this. -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
