Re: git: 61e4a788ecab - main - ports-mgmt/dialog4ports: mark as deprecated and broken on current

From: Baptiste Daroussin <bapt_at_freebsd.org>
Date: Thu, 21 Dec 2023 15:51:38 UTC 
On Thu, Dec 21, 2023 at 04:23:58PM +0200, George L. Yermulnik wrote:
> Hello!
> 
> On Thu, 21 Dec 2023 at 15:03:26 (+0100), Baptiste Daroussin wrote:
> 
> > First clearly none of those looks shitty to me!
> 
> > Anyway according to you which one do you fine neater and more convenient ?
> 
> > - https://bapt.nours.eu/1.png
> > - https://bapt.nours.eu/2.png
> 
> Well, your pictures look a way better than what I see on my end =(
> Here's my mileage (it might obviously be something with my terminal app (I use `mlterm`), but anyways):
> - dialog4ports: https://i.imgur.com/cZHLBN4.png
> - portconfig: https://i.imgur.com/0xKF3f1.pngO
>   - portconfig with "D4PASCIILINES=yes" set just fails and breaks
>     terminal so I need to `reset` it afterwards: https://i.imgur.com/zg85JsW.png
> 
> ps: I must admit that I'm on an outdated version of FreeBSD though and
> this may be a culprit for the `portconfig` to display port options
> properly (whilst `dialog4ports` has no issues like that at all). So my
> UX may not be taken into account (EOL'ed versions of FreeBSD aren't
> supported), while I'd really be keen to keep `dialog4ports` as the only
> decent port config management UI for me. If possible. Thanks.

Right now bsd.port.mk do accept both portconfig and dialog4ports, so if can use
either of them if they are installed, just install dialog4ports and ignore
portconfig.

As for supporting earlier EOLed versions of freebsd the issue probably stands
in the version of ncurses and how it is used by libbsddialog, probably something
that it is not worth investigated, of course if the people interested in having
those unsupported environement are investigating and providing a patch I am
sure, portconfig upstream would be happy to integrate it.

I don't think it is worth fixing, Just keep using dialog4ports, you can see
there are no EXPIRATION_DATE for now only a deprecation notice, so not it is not
yet planned to remove it yet.

Best regards,
Bapt