Date: Sat, 23 Nov 2013 12:11:08 +0000 From: Steve O'Hara-Smith <steve@sohara.org> To: Frank Volf <frank@deze.org> Cc: freebsd-questions@freebsd.org Subject: Re: Building ports in jails after staging support Message-ID: <20131123121108.02533a32a72bf17ad6ffd45a@sohara.org> In-Reply-To: <529083BA.7060601@deze.org> References: <52862B79.5060603@deze.org> <529083BA.7060601@deze.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 Nov 2013 11:30:18 +0100 Frank Volf <frank@deze.org> wrote: > Anybody r this question? > I'm really struggling with it. Not directly, I stopped building ports inside jails (except for port building jails) some time back. These days I use poudriere on a build machine to build all the ports I want built with my chosen options and present them in a package repository which I export by http with thttpd (any web server will do). Then all my jails and machines (physical or virtual) have a file /usr/local/etc/pkg.conf with one line setting packagesite to point to my repository. Once set up it's very easy to manage, updating the repository is as simple as: poudriere ports -u poudriere bulk -f <file with list of wanted packages> -j build Updating a jail or machine: pkg upgrade Possibly twice if pkg itself is updated. I have in the past needed to add a -f to force it to update everything but not for a while now so whatever caused that problem is probably fixed. The level of pain is vastly reduced compared to the old days of portupgrade. The only tricky bit is the need to use multiple repositories if you want to have multiple builds of the same port available which complicates the build arrangements a bit and the pkg configuration. I haven't needed to do that so I can't say just how fiddly it would be, but it looks to be fairly straightforward. > Regards, > > Frank > > Op 15-11-2013 15:11, Frank Volf schreef: > > > > Hi, > > > > I'm having a FreeBSD 9.1-RELEASE system with some jails. > > The jails have problems building/upgrading ports after staging support > > was added to the /usr/ports tree. > > I'm using portupgrade for the upgrades (but that is not political, if > > another tool does the job then that is fine as well). > > > > I searched the archives of this list and if I understood that there > > are two problem areas: > > 1) All jails share a union-mounted read-only copy of the /usr/ports > > tree, and staging tries by default to write in /usr/ports > > 2) My jails are build according to the description in the FreeBSD > > handbook and the symbolic link in the jails that points usr/local to > > ../s/usr-local is causing problems as well. > > > > I found several messages from people describing work-arounds (e.g. > > setting PACKAGES or NO_STAGE in /etc/make.conf), adjusting PREFIX in > > pkgtools.conf. > > Some messages seem to be contradicting each other (like NO_STAGE > > should not be defined), and some solution only solve one of the two > > problems. > > > > So, my question is simply: is there an official (future proof) way how > > to fix this? In other words, what should I do to get portupgrade or > > any other port mgmt tool working again in the jails with my setup? > > > > Regards, > > > > Frank > > > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "freebsd-questions-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131123121108.02533a32a72bf17ad6ffd45a>