Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Feb 2024 10:50:13 -0800
From:      John Hixson <jhixson@freebsd.org>
To:        Michael Osipov <michaelo@freebsd.org>
Cc:        Gleb Popov <arrowd@freebsd.org>, ports-committers@freebsd.org,  dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org
Subject:   Re: Re: git: ece1cb52e7ff - main - security/sssd: mark port deprecated
Message-ID:  <6ecpzfhdipmjvxwqabxohzam4uyzwtjomizvm73ttofutcu37g@odfxr2idgp64>
In-Reply-To: <16f9baa7-1e25-49d9-9f31-0aafd528250a@FreeBSD.org>
References:  <202402030553.4135rFLH050086@gitrepo.freebsd.org> <CALH631kLSy5rBFtXsUbDeXUQ-8P3oWZ6pkN6Tz%2BTwinnifNd6w@mail.gmail.com> <a7ee24f4-2ba3-4bb4-a306-0ed89728ab8a@FreeBSD.org> <cy3g5xomwle67x3h2spzd67hzjweojiubw5op3ka2h5szwoz5c@t4sbqefurn6c> <16f9baa7-1e25-49d9-9f31-0aafd528250a@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--v2emordw2stsfllw
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 07, 2024 at 07:09:13PM +0100, Michael Osipov wrote:
> >=20
> > 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?
>=20
> I see your point it is partially valid to me. I'd expect sssd-devel to fo=
rm
> 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. Wh=
en
> 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.
>=20

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

Cheers,

- John


--v2emordw2stsfllw
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQKTBAABCgB9FiEEJaAswQZQMflCdCA6RqljBb/iPUAFAmXD0N9fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDI1
QTAyQ0MxMDY1MDMxRjk0Mjc0MjAzQTQ2QTk2MzA1QkZFMjNENDAACgkQRqljBb/i
PUDF4BAAgD5ksQ93mxmrWpsxZnXYs8Zfcc7VVcYASKLSo75cuqJIbKs+PmUypMSJ
wLuhNw4tLAZFtC6nX80Sbf9yaTUH3DoU4xCz3ROk02GRvDWzyP8aEBc1S2SjQvL3
kkS3LH0H0JmVw+uR2cp2yN2oqOa9kmVU6zX80k7IcEODfFqtFq4dPlvaEQoqSAYv
PmxvnFJgxO+6kps7lpQftOwKxWAE9WQ7CB6XyNDE6gyuzAVavAZZbaGrCAK3Aooz
p+UP1WZbj8yNCNqGu2nw9NiwMCmGCdzUkUgJCSQeL+6rlUvSF8JzXUgnUD0CA9dr
z4xGOaJAJZ7eYQvwMlqg6E7PAUEysSljDlG+DR5Qvh6fCrfa+CJDZV10hv96ThbN
p1NNUKQQXci0b7LkIHzV0ohB5Uerw9dfA0s1JnhpxyZ9ut+PTmoW8lrA818naT2R
qB7lBQ6dgyAsbPe7ZYYe9wz3Xd32d04WVWZq4BvQNruX37Fqptlq3s2+oKAJJOcH
nj6Ba58XSYUS3GP6gbz6WB8KhB/5umALdsux7ur+EqZS3Sx4xhmjKf5n2VvrfkGM
qnyJD1JosI72mMvY0RDyx1EvJAqxP+QbDmp2PhTsU6Q2F5wd3wkp0yfPivysJTnQ
kzpjARbM98/7MuOJHBQJj0x4KqAjQogejhppR5/ByZjIc4qjgc8=
=DID7
-----END PGP SIGNATURE-----

--v2emordw2stsfllw--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ecpzfhdipmjvxwqabxohzam4uyzwtjomizvm73ttofutcu37g>