[pacman-dev] Info pages install template(was: alpmtrigger: triggering events after all packages got installed...)
On Fri, Sep 11, 2009 at 8:27 AM, Allan McRae <allan@archlinux.org> wrote:
Given all we need to currently do for the install file for info pages is to copy the prototype and list the info pages to install, you suggestion really is no less work.
On this note, the template has a rather unfortunate side effect in that it is not #!/bin/sh compatible, unless that happens to be linked to bash. Epic fail every time I install a package with info pages on my system that has /bin/sh linked to /bin/dash, it is really quite a shame... The shift crud left behind does not help the situation either. -Dan
On Fri, Sep 11, 2009 at 3:33 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Fri, Sep 11, 2009 at 8:27 AM, Allan McRae <allan@archlinux.org> wrote:
Given all we need to currently do for the install file for info pages is to copy the prototype and list the info pages to install, you suggestion really is no less work.
On this note, the template has a rather unfortunate side effect in that it is not #!/bin/sh compatible, unless that happens to be linked to bash. Epic fail every time I install a package with info pages on my system that has /bin/sh linked to /bin/dash, it is really quite a shame...
The shift crud left behind does not help the situation either.
Just fixing template would not get all scriptlets fixed though. We would really need to have someone look at all scriptlets in svn, and fix all these problems in once, as in http://bugs.archlinux.org/task/13803 :) By the way, I am against this info pages scriptlet, it causes a lot of work to packagers for very little benefit. If people care about the info index, they can maintain it themselves. But if packagers think this is an important point, then it should be a motivation to think about an easier and more global way to handle it.
On Fri, Sep 11, 2009 at 07:17:57PM +0200, Xavier wrote:
By the way, I am against this info pages scriptlet, it causes a lot of work to packagers for very little benefit. If people care about the info index, they can maintain it themselves. But if packagers think this is an important point, then it should be a motivation to think about an easier and more global way to handle it.
I agree that this is something that should be made easier and *possibly* even configurable for those that don't care about info pages (though the speedup will be very negligible), but ignoring it from the packaging aspect completely is really no different than saying, "Let's not bother updating ld.so.cache after installing a library. If the user wants to use a just-installed library let them run ldconfig themselves." Granted, this is a contrived example, but the package management software must deal with all aspects of installing package X regardless of personal preferences (even if dealing with it means a way of letting people ignore a given feature). -- Jeff My other computer is an abacus.
participants (3)
-
Dan McGee
-
Jeff
-
Xavier