Date: Thu, 19 May 2005 19:55:08 +0200 From: Erik Trulsson <ertr1013@student.uu.se> To: Tony Shadwick <tshadwick@goinet.com> Cc: freebsd-questions@freebsd.org Subject: Re: Shared /usr/ports directories Message-ID: <20050519175508.GA25517@falcon.midgard.homeip.net> In-Reply-To: <20050519120624.X62516@mail.goinet.com> References: <428CC15A.8030600@ntlworld.com> <20050519165710.GA25173@falcon.midgard.homeip.net> <20050519120624.X62516@mail.goinet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 19, 2005 at 12:07:51PM -0500, Tony Shadwick wrote: > Does this impact the pkgdb? To be honest, I don't know where the > information that pkg_info returns is stored. :) Probably should have > sought this out a long time ago, but hey, I'm lazy. I don't know anything about pkgdb, but the information that pkg_info returns is stored in /var/db/pkg, and options set via the OPTIONS system in ports are stored in /var/db/ports. If you were to use portupgrade (which most people seem to use, but which I don't use) things might be different - I don't know. For me the only things stored in /usr/ports are the port skeletons themselves. (/usr/ports/distfiles is just a symlink on my system to a directory on another filesystem.) > > Tony > > On Thu, 19 May 2005, Erik Trulsson wrote: > > >On Thu, May 19, 2005 at 05:39:54PM +0100, Richard Danter wrote: > >>Hi all, > >> > >>I have several machines running FBSD now. At the moment I have a > >>complete ports tree on each machine. I was wondering if it was possible > >>to have it all on just one machine and NFS mount it? > > > >That is certainly possible. > > > >> > >>I have already been doing this for the /usr/ports/distfiles directory, > >>but had not shared everything else as I was not sure if settings from a > >>build on one machine may cause problems when building on another machine. > >> > >>Each machine has it's own /etc/make.conf with settings such as the > >>processor type, so it is important that one build can't effect another. > > > >I would suggest you set WRKDIRPREFIX in /etc/make.conf so that the > >files built by the ports system do not get placed under /usr/ports but > >somewhere else. > >For example I have 'WRKDIRPREFIX=/var/workdir' in my /etc/make.conf. > >That way all the files that are created when you build a port ends up > >under /var/workdir rather than under /usr/ports. If WRKDIRPREFIX is > >set to a directory on a local filesystem there will be no way for a > >build on one system to affect one on another. You should even be able > >to export /usr/ports as read-only. > >(Changing WKRDIRPREFIX also makes it a lot easier and faster to clean > >up after building ports. Instead of having to issue a 'make clean' for > >each port built, you can just do a 'rm -fr /var/workdir/*' and all the > >workdirs will be removed quickly.) -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050519175508.GA25517>