Re: Re: git: ece1cb52e7ff - main - security/sssd: mark port deprecated

From: John Hixson <jhixson_at_freebsd.org>
Date: Wed, 07 Feb 2024 18:00:20 UTC
On Tue, Feb 06, 2024 at 11:23:45AM +0100, Michael Osipov wrote:
> On 2024-02-03 07:25, Gleb Popov wrote:
> > On Sat, Feb 3, 2024 at 8:53 AM John Hixson <jhixson@freebsd.org> wrote:
> > > 
> > > The branch main has been updated by jhixson:
> > > 
> > > URL: https://cgit.FreeBSD.org/ports/commit/?id=ece1cb52e7ffa225bc1c8ed659c5974ef1c0088d
> > > 
> > > commit ece1cb52e7ffa225bc1c8ed659c5974ef1c0088d
> > > Author:     John Hixson <jhixson@FreeBSD.org>
> > > AuthorDate: 2024-02-03 05:51:53 +0000
> > > Commit:     John Hixson <jhixson@FreeBSD.org>
> > > CommitDate: 2024-02-03 05:51:53 +0000
> > > 
> > >      security/sssd: mark port deprecated
> > > 
> > >      - Very old version of this port no longer supported
> > >      - sssd-devel has current versions
> > 
> > Why not just update this port to the devel version?
> 
> I agree with Gleb. This is unnecessarily confusing and many will likely
> refuse to use a -devel port in production. Other ports do have regular ports
> and real -devel ports as well. For me, this violates POLA somewhat.
> 
> M

What is the proper route to take here? sssd-devel isn't really a "devel"
port. It's just the up to date version of sssd. The current sssd port is
very old (like 5 years or more). I would like to just replace it with
the new version but don't want to force an update for anyone who may
rely on it. Should sssd-devel be renamed sssd2 and sssd be renamed sssd1
or some such? What is this POLA that I am possibly violating by the way?

Thanks,

- John