Unless say, you're doing package installation outside of a chroot/jail, to populate something inside a chroot/jail before you start said chroot/jail. Adrian On 17 July 2011 00:13, Chris Rees <crees_at_freebsd.org> wrote: > On 16 Jul 2011 17:04, "Stephen Montgomery-Smith" <stephen_at_missouri.edu> > wrote: >> >> On 07/16/2011 10:53 AM, Chris Rees wrote: >>> >>> >>> On 16 Jul 2011 16:38, "Stephen Montgomery-Smith" <stephen_at_missouri.edu >>> <mailto:stephen_at_missouri.edu>> wrote: >>> > For example, suppose the C source code contains something like: >>> > char applications_dir = "/usr/local/share/applications"; >>> > and this is filled in by the ./configure script. >>> > >>> > How is that handled? >>> > >>> >>> It's not. >>> >>> Remember what a package is, literally the files from the plist tarred >>> with some magic +FILEs and the pkg-*install files- if paths are >>> hardcoded in objects that's how it'll be installed. >> >> >> What if some of the installation programs are binaries, and "/usr/local" > is hard coded into installation binaries or scripts provided by the software > itself. > > Sorry, poor wording on my part. > > If it was compiled as prefix=/usr/local, that's how it'll be installed, > regardless of your -p argument. > > Chris > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Sun Jul 17 2011 - 00:02:41 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:15 UTC