Date: Wed, 6 Mar 2019 16:11:27 -0500 From: Paul Mather <freebsd-lists@gromit.dlib.vt.edu> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: poudriere(-devel) ports updating question Message-ID: <85643302-A1F8-4EF2-B75D-3FAF3A138923@gromit.dlib.vt.edu> In-Reply-To: <20190306205827.GA34798@rpi3.zyxst.net> References: <20190305140939.GA18890@rpi3.zyxst.net> <30D9DC41-0FE6-4B2F-846B-E7E1BDEF485D@lassitu.de> <20190306205827.GA34798@rpi3.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 6, 2019, at 3:58 PM, tech-lists <tech-lists@zyxst.net> wrote: > On Wed, Mar 06, 2019 at 06:23:49PM +0100, Stefan Bethke wrote: >>> Am 05.03.2019 um 15:09 schrieb tech-lists <tech-lists@zyxst.net>: >=20 >>> Basically I'm looking for exclude mask functionality when updating a >>> ports tree with poudriere ports. >>>=20 >>> Do I need to do this manually or have I missed something? >>=20 >> I don=E2=80=99t think it=E2=80=99s easy to do that. How would you = handle dependencies? (For example, some ports require X11 libs and = stuff, even though they=E2=80=99re in a different category.) >=20 > You're right of course. My logic was wrong, and wrong premise[1] = because I > was stuck on thinking a bulk -a build. But I found how to do it (to = remove categories) in case anyone is interested. The key is in the > method used to update the tree, which is svn+https. >=20 > so, from the top of the ports tree, svn update --set-depth=3Dexclude = biology would exclude the biology category permanently. svn update = --set-depth=3Dinfinity biology would re-add it. > svn update --set-depth=3Dinfinity would make it be like nothing was > excluded in the first place. >=20 > but on reflection, it breaks a little of the ports infrastructure and = I > don't want to do that. That's correct: omitting parts of the ports hierarchy might break a = particular ports build catastrophically. If you're looking to exclude certain functionality when building ports = you should investigate using ports options to achieve that. For example, I have a poudriere jail called "trurl" that is a headless = system on which I don't want to use X11. I also don't want to use CUPS = for that matter. So, in its "trurl-make.conf" file I include this line: OPTIONS_UNSET_FORCE=3D X11 CUPS That will force those options off for all ports. The result is I don't = get any ports built supporting those options. I guess it's not foolproof, but it seems to work well enough for me. I hope this helps. Cheers, Paul.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85643302-A1F8-4EF2-B75D-3FAF3A138923>