On Do, 12 Mär 2009, Raphael Hertzog wrote: > I would rather have the new install-info in /usr/bin/, and dpkg > ships an /usr/sbin/install-info that does nothing but calls > /usr/bin/install-info if it exists and warn otherwise. (And also warn if > it's called with the full path).
That sounds fine for me, too. But should we ship the wrapper or GNU install-info itself as /usr/bin/install-info? If we can assure that the /usr/sbin/install-info is called from the maintainer scripts (there /usr/sbin should be in front of /usr/bin) I could simply drop the install-info wrapper I posted and install GNU i-i as /usr/bin/install-info. Maintainer scripts will call /usr/sbin/install-info that can: - warn to upgrade the package if that magic envvar is set - warn to use /usr/bin/install-info if called with absolute path but outside maintainer scripts - if all that does not happen simply call /usr/bin/install-info (because root/admin called install-info without absolute path). > How does that sound ? Very good. What about my proposal above? Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining <[email protected]> Vienna University of Technology Debian Developer <[email protected]> Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- Stay the patient course. Of little worth is your ire. The network is down. --- Windows Error Haiku -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
