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

On Wed, Feb 07, 2024 at 07:09:13PM +0100, Michael Osipov wrote:
> > 
> > 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?
> 
> I see your point it is partially valid to me. I'd expect sssd-devel to form
> off a non-release version, namely a Git hash. As for security/sssd: Almost
> just like you said. Deprecate and introduce security/sssd2. Very similar to
> what security/krb5* or security/openssl* are don't. That scheme would
> resemble. I wouldn't touch security/sssd in terms of renaming anymore. When
> sssd 3 comes out, you can have another parallel port for that.
> POLA violation for me is that an apparently valid port is replaced with a
> devel one.
> 

Thanks for the clarification. I'll get this sorted out by this weekend.

Cheers,

- John