Date: Sat, 6 Jan 2024 00:05:17 +0100 From: Peter <pmc@citylink.dinoex.sub.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: freebsd-stable@freebsd.org, bapt@freebsd.org, alfix86@gmail.com, asiciliano@freebsd.org Subject: Re: ports-mgmt/portconfig surprize Message-ID: <ZZiLLbNeJZ44TXAb@disp.intra.daemon.contact> In-Reply-To: <20240105155617.03436679@slippy.cwsent.com> References: <ZZdAz2EM2htYzfX9@disp.intra.daemon.contact> <20240105155617.03436679@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 05, 2024 at 07:56:16AM -0800, Cy Schubert wrote: ! ! This should have been posted to freebsd-ports@. Next time use the correct ! ML. Hi, I was thinking -ports is for malfunctioning individual ports. Whereas the matter at hand is about general infrastructure (every server needs some ports) and deploy. I currently have no idea where to find the people interested in that, but the port options setting being unconditionally interactive is a conflict with any automated deploy. I always have to hack and refactor this - and that new tool doesn't improve anything (in that regard), it just adds some malfunction (and forces me to understand the new code). But okay, when I'm in a relaxed mood again I will try and do a writeup of the issue and send it to -ports. Let's see if anybody there is interested... cheers, PMc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZZiLLbNeJZ44TXAb>