From owner-freebsd-questions@freebsd.org Wed Mar 6 17:23:54 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20B9415206C4; Wed, 6 Mar 2019 17:23:54 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E6AD39521E; Wed, 6 Mar 2019 17:23:52 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 3AF8C1D2D09; Wed, 6 Mar 2019 17:23:50 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: poudriere(-devel) ports updating question From: Stefan Bethke In-Reply-To: <20190305140939.GA18890@rpi3.zyxst.net> Date: Wed, 6 Mar 2019 18:23:49 +0100 Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <30D9DC41-0FE6-4B2F-846B-E7E1BDEF485D@lassitu.de> References: <20190305140939.GA18890@rpi3.zyxst.net> To: tech-lists X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: E6AD39521E X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of stb@lassitu.de designates 2a00:14b0:4200:32e0::1ea as permitted sender) smtp.mailfrom=stb@lassitu.de X-Spamd-Result: default: False [-1.02 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.89)[-0.888,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[lassitu.de]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.77)[0.772,0]; NEURAL_HAM_LONG(-0.94)[-0.938,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[gilb.zs64.net]; IP_SCORE(-0.15)[ipnet: 2a00:14b0::/32(-0.44), asn: 13135(-0.31), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13135, ipnet:2a00:14b0::/32, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Mar 2019 17:23:54 -0000 > Am 05.03.2019 um 15:09 schrieb tech-lists : >=20 > Hi, >=20 > There are several categories of ports I'd like to avoid for some > architectures. For example, I don't want x11 for mips.mips64. Or = astronomy. But let's say, for this architecture, I want to build = everything else. >=20 > I can't see a way of excluding categories with poudriere ports when > updating the ports tree - the only workaround I can see is to download = another tree, call it something and then manually edit that tree, and = then set the build off with -p port-treename. Every time I want to > make a bulk run. >=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? 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.) Do you want to save time on builds by excluding pkgs that you know = you=E2=80=99ll never need? Or what is your goal with this? In my setup, I rely on the regular packages from the official repo, but = for those pkg that I need built with different options, I run a custom = list. You could try to produce a filtered list of all ports, removing those = that you=E2=80=99d never select manually, and let poudriere figure out = what needs to be built. Something along the lines of: - update ports - list all ports | grep -v '^x11/' - run poudriere with resulting list Stefan --=20 Stefan Bethke Fon +49 151 14070811