Subject: Re: make update hell
To: Ben Collver <firstname.lastname@example.org>
From: Pavel Cahyna <email@example.com>
Date: 10/08/2004 17:33:45
> > How does "build.sh -U sets" get setuid executables for packaging NetBSD?
> It uses a combination of special command line arguments for BSD install,
> and pax. The install arguments are -U and -M, and the pax argument is
> -M. This causes file ownership and permissions data to be kept in a log
> file rather than in the filesystem itself. One benefit of doing it this
> way is that it does not depend on support for shared libraries.
And the disadvantage for pkgsrc is that not all packages use only pax and
install, I suppose... What about having the ownership and permissions (at
least the non-standard ones, like setuid/setgid/other than root:wheel) in
pkgsrc together with PLIST?