From nobody Tue Feb 20 13:13:06 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TfKb66k8Xz5C3Cf for ; Tue, 20 Feb 2024 13:13:06 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4TfKb659y2z4xpN for ; Tue, 20 Feb 2024 13:13:06 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: X-Catflap-Envelope-To: freebsd-ports@FreeBSD.org Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 41KDD6pF013502; Tue, 20 Feb 2024 13:13:06 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 41KDD6G2013501; Tue, 20 Feb 2024 13:13:06 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202402201313.41KDD6G2013501@donotpassgo.dyslexicfish.net> Date: Tue, 20 Feb 2024 13:13:06 +0000 Organization: Dyslexic Fish To: marklmi@yahoo.com, dewaynegeraghty@gmail.com Cc: rozhuk.im@gmail.com, freebsd-ports@FreeBSD.org, aryehfriedman@gmail.com Subject: Re: FreeBSD ports community is broken [port building configuration notes] References: <87B38D6C-1D83-4158-B03B-F4C8EA396DD1.ref@yahoo.com> <87B38D6C-1D83-4158-B03B-F4C8EA396DD1@yahoo.com> <20240219104333.6ecff336@rimwks.local> <8C4AB1AF-139D-4144-867C-6AD1AE1E1307@yahoo.com> <7B21AFF0-E0D5-4836-8486-F812E79152DF@yahoo.com> In-Reply-To: <7B21AFF0-E0D5-4836-8486-F812E79152DF@yahoo.com> User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Tue, 20 Feb 2024 13:13:06 +0000 (GMT) X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4TfKb659y2z4xpN X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US] Mark Millard wrote: > It probably should be separate from this topic, but I'd interested > to understand some example types of changes folks make for which > poudriere prevents the changes from working but for which portmaster > use or make use allows the change to work. I've many changes, nothing that would upset poudriere though. I've probably grasped the wrong ideas from this thread. I thought it was about the implied effective deprecation of the ports infrastructure for a binary package only structure, with poudriere being used to create custom packages in any way it wants going forward. If pordriere continues to build via the make system we have already, then I can't see any issue. What's the reasoning behind people claiming a shift from "make install" to poudriere is necessary? Cheers, Jamie