Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Nov 2013 11:30:18 +0100
From:      Frank Volf <>
Subject:   Re: Building ports in jails after staging support
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

Anybody for this question?
I'm really struggling with it.



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
> _______________________________________________
> mailing list
> To unsubscribe, send any mail to 
> ""

Want to link to this message? Use this URL: <>