Re: ports-mgmt/portconfig surprize

In message <ZZiLLbNeJZ44TXAb@disp.intra.daemon.contact>, Peter writes:
> 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

portconfig and dialog4ports are not part of FreeBSD base. Both ports and it 
is the ports infrastructure, in /usr/ports/Mk, that calls them.  
Complaining about them on -current or -stable is a waste of everyone's time 
and will fall on deaf ears.

portmgr made the decision to deprecate dialog4ports on Tue Oct 10 13:53:44 
2023 (in /usr/ports/Scripts/dialog4ports.sh). If you have concerns about 
it, that's the forum to discuss it, or a PR.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  https://FreeBSD.org
NTP:           <cy@nwtime.org>    Web:  https://nwtime.org

			e^(i*pi)+1=0