Re: git: bb63e82e8c10 - main - bsddialog(1): document the replacement of dialog(1)

On Tue, 10 Oct 2023 15:53:45 +0200
Baptiste Daroussin <bapt@freebsd.org> wrote:

> On Tue, Oct 10, 2023 at 10:49:39PM +0900, Tomoaki AOKI wrote:
> > On Tue, 10 Oct 2023 13:59:09 +0200
> > Baptiste Daroussin <bapt@freebsd.org> wrote:
> > 
> > > On Tue, Oct 10, 2023 at 12:03:32PM +0200, Herbert J. Skuhra wrote:
> > > > On Tue, 10 Oct 2023 09:25:13 +0200, Baptiste Daroussin wrote:
> > > > > 
> > > > > The branch main has been updated by bapt:
> > > > > 
> > > > > URL: https://cgit.FreeBSD.org/src/commit/?id=bb63e82e8c109156b31e806fac8ecefbd259a0ed
> > > > > 
> > > > > commit bb63e82e8c109156b31e806fac8ecefbd259a0ed
> > > > > Author:     Baptiste Daroussin <bapt@FreeBSD.org>
> > > > > AuthorDate: 2023-10-10 07:24:25 +0000
> > > > > Commit:     Baptiste Daroussin <bapt@FreeBSD.org>
> > > > > CommitDate: 2023-10-10 07:24:25 +0000
> > > > > 
> > > > >     bsddialog(1): document the replacement of dialog(1)
> > > > > ---
> > > > >  RELNOTES |  3 +++
> > > > >  UPDATING | 10 ++++++++++
> > > > >  2 files changed, 13 insertions(+)
> > > > > 
> > > > > diff --git a/RELNOTES b/RELNOTES
> > > > > index c5686a4f30fb..880cec5d3fe1 100644
> > > > > --- a/RELNOTES
> > > > > +++ b/RELNOTES
> > > > > @@ -10,6 +10,9 @@ newline.  Entries should be separated by a newline.
> > > > Herbert
> > > > >  
> > > > >  Changes to this file should not be MFCed.
> > > > >  
> > > > > +ff01d71e48d4:
> > > > > +	dialog(1) has been replace by bsddialog(1)
> > > > > +
> > > > >  41582f28ddf7:
> > > > >  	FreeBSD 15.0 will not include support for 32-bit platforms.
> > > > >  	However, 64-bit systems will still be able to run older 32-bit
> > > > > diff --git a/UPDATING b/UPDATING
> > > > > index a1bcecadd357..0064e53c7a53 100644
> > > > > --- a/UPDATING
> > > > > +++ b/UPDATING
> > > > > @@ -27,6 +27,16 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW:
> > > > >  	world, or to merely disable the most expensive debugging functionality
> > > > >  	at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
> > > > >  
> > > > > +20231010:
> > > > > +	dialog(1) has been replaced in base by bsddialog(1), while most of the
> > > > > +	time replacing a dialog(1) call by a bsddialog(1) call works out of the
> > > > > +	box, bsddialog(1) is not considered as a drop-in replacement dialog(1).
> > > > > +
> > > > > +	If you do depend on dialog(1) functionnality, please install cdialog
> > > > > +	from ports:
> > > > > +
> > > > > +	pkg install cdialog
> > > > > +
> > > > >  20230927:
> > > > >  	The EARLY_AP_STARTUP kernel option is mandatory on x86.  The option
> > > > >  	has been added to DEFAULTS, so it should automatically be included in
> > > > 
> > > > This breaks ports-mgmt/dialog4ports.
> > > > 
> > > > Installing devel/cdialog (via pkg) and patching
> > > > work/dialog4ports-0.1.6/Makefile obviously resolves this issue:
> > > > 
> > > > -LDADD+=        -ldialog
> > > > +LDADD+=        -L/usr/local/lib -lcdialog
> > > > 
> > > > Or is the port obsolete/to be replaced?
> > > > 
> > > > --
> > > > 
> > > 
> > > Oups thank you! yes this is replaced by ports-mgmt/portconfig.
> > > 
> > > Best regards,
> > > Bapt
> > 
> > Is there any plan to include ports-mgmt/portconfig into base?
> > To do so, options menu can be used out of box, witout needs to install
> > ports-mgmt/dialog4ports manually.
> > 
> > It's licensed as BSD2CLAUSE and working fine for me until it first
> > appears on ports.
> > 
> > # IIRC, dialog4ports was not incorporated to base because it requires
> > # GNU dialog and GNU dialog was going to be removed from base.
> > # Now we have 2 ways, portconfig to be default and incorporated into base,
> > # and incorporating dialog4ports into base with fixing to use bsddialog.
> > 
> > BTW, is it possible to show that each option is on default or not?
> > It would help determining changes to default.
> > 
> > Regards.
> 
> I don't have any plan for that, I like the way it works now, like pkg in the
> end.
> 
> if we want to add new feature for it we don't have to wait all the supported
> version of freebsd to have the latest version of portconfig.
> 
> Best regards,
> Bapt

Ah, having bootstrap on base and keeping itself in ports/pkgs like pkg
would be fine, unless portconfig itself happen to have build options.
(For example, static linking optin.) It can cause chicken-and-egg (or
lock the key in the car) dilemma. Maybe it would be a corner case that
cannot access to pkg repo or before RC for .0 releases that pkg is not
yet provided.

Regards.

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>