On Sun, Feb 5, 2017 at 11:28 PM, Kevin Kofler <kevin.kof...@chello.at> wrote: > Tom Hughes wrote: >> I believe it's referring to the use of /usr/bin/env as mentioned here: >> >> https://fedoraproject.org/wiki/Script_Interpreters_(draft) > > Note that this is a draft guideline that was voted down: > https://meetbot.fedoraproject.org/fedora-meeting/2009-08-19/fedora-meeting.2009-08-19-16.01.log.html#l-38 > It got only -1 votes, not a single +1. > > So this is NOT an enforced guideline and it is IMHO a bug in rpmlint that it > complains about it. > >> Although I think that draft guideline is outdated and the auto requires >> logic does now handle it - although /usr/lib/rpm/script.req has a TODO >> comment to fix it there does also seem to be code to handle it. > > The code handles only the case where what comes after /usr/bin/env is an > absolute path, which defeats the point of using /usr/bin/env to begin with. > > Mageia has a fix that makes it work right: > http://svnweb.mageia.org/packages/cauldron/rpm/current/SOURCES/script-env.diff?view=markup >
I'm working on an upstreamable version of the fix, as the version shipped in Mageia is dependent on changes to dependency generators that are quite undesirable upstream. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
