www/nginx pkg-plist + pkgng (detectable?)
bapt at freebsd.org
Wed Apr 10 11:55:44 UTC 2013
On Wed, Apr 10, 2013 at 09:02:29AM +0100, Chris Rees wrote:
> On 10 April 2013 07:13, Baptiste Daroussin <bapt at freebsd.org> wrote:
> > On Tue, Apr 09, 2013 at 08:59:50PM +0200, Michael Gmelin wrote:
> >> On Tue, 9 Apr 2013 19:43:15 +0100
> >> Chris Rees <utisoft at gmail.com> wrote:
> >> >
> >> > No, it's a bug in pkgng; it should respect @cwd.
> >> >
> > No it is not.
> > While i agree with pkgng that should repect @cwd (it surely does)
> > There is nothing written anywhere that will waranty you that the @exec line will
> > be parsed in order ro prepend @cwd path to a path you provide. the only thing
> > doing that is %D.
> > A user MUST add %D and have complete path in @exec lines
> > In fact in that case it works by chance becauce of how pkg_install treat plist.
> Am I misunderstanding the meaning of "current working directory"?
> When mkdir is called, it should create the directory in @cwd.
> pkg_install's behaviour is correct here, and pkgng's is not.
Now one of the major difference between pkg_* and pkgng is that plist is no more
a script, as it should have never been meaning current directory means nothing.
As all of the plist (meaning 99%) of the uses the %D as they should do and %D is
expected to the lastet @cwd "path" then it works correctly.
keeping plist as a script is a total non sense and has been avoided by most of
the maintainer for the last years (almost noone used @cwd that way) for good
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
More information about the freebsd-ports