Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Aug 2020 17:25:28 +0300
From:      Lev Serebryakov <lev@FreeBSD.org>
To:        Niclas Zeising <zeising@freebsd.org>, Greg 'groggy' Lehey <grog@FreeBSD.org>
Cc:        FreeBSD Developers <developers@freebsd.org>, ports@freebsd.org
Subject:   Re: Aggressive ports removal
Message-ID:  <ebf99712-b9f6-1438-320d-9f25050f3b8a@FreeBSD.org>
In-Reply-To: <f9cd7c4d-9477-89ab-f054-75b9bf9ca077@freebsd.org>
References:  <202008291154.07TBsr7L086597@repo.freebsd.org> <FC66C7DA-2A0D-43E7-B29C-E4C94C1973BA@freebsd.org> <f56625f8-1d63-515c-93af-909a4e47e65d@freebsd.org> <9a4583d9-097e-d0ba-4959-5c4d7b96b611@freebsd.org> <20200829232707.GC46173@eureka.lemis.com> <f9cd7c4d-9477-89ab-f054-75b9bf9ca077@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--XKGBaeSHJygJcraFqtFAg4k3MxXFk4tBs
Content-Type: multipart/mixed; boundary="aV4iVmHneUOgjEKWdjv6YrUc7KKlpLo70"

--aV4iVmHneUOgjEKWdjv6YrUc7KKlpLo70
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 30.08.2020 11:28, Niclas Zeising wrote:

>> Exactly.=C2=A0 Another case in point: x11/xtset.=C2=A0 Maintenance sto=
pped in
>> 1993, 11 days after the FreeBSD project came into existence.=C2=A0 It =
works
>> fine, and I find it very useful.=C2=A0 If at some time in the future i=
t
>> should no longer work with the latest and greatest iteration of the C
>> programming language or ports structure, that shouldn't be a reason to=

>> discard it.
>=20
> Then it is very easy.=C2=A0 If it is useful to you, adopt it as maintai=
ner, then you will get a notification if it fails to build, and you can f=
ix the issue(s)
 It is not "very easy".
 What if port which is like `x11/xtset` is used by 100 users and 0 develo=
pers/committers?
 What should these 100 users (not programmers by any means) do when next =
`pkg upgrade` will try to delete this package?

 `-fcommon/-fno-common` and nay other infrastructure/compiler changes ARE=
 NOT user-visible problems, and MUST NOT be transferred to users.

 Unpatched security vulnerabilities ARE user-visible problems. Our develo=
pers' dances around C/C++ standards and other hacker toys ARE NOT.

--=20
// Lev Serebryakov


--aV4iVmHneUOgjEKWdjv6YrUc7KKlpLo70--

--XKGBaeSHJygJcraFqtFAg4k3MxXFk4tBs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAl9NCF5fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5
NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c
R48eyg/9FX3HCMKHNbDN2qIOrkRKYnaJFKz7Ilbh39iGmHEyVTCWa2wm+7S7ma+8
dIIhkw9GZu8d8B6633L/j1kQLZbtp5clvT1Ct+goV6STdI47quSWEdKO9msy8HzR
6ryGZzx4/PqHOkZQh8UBrKPFX3OYazYppXki9jrKT9NIGDa38Q4YyI4zP3YEyIAT
cBF1S14haTGvOPP0TE2Ie3srlwgb7Fc0RaIx5JOcnNZ0ySZ+nOstKvHCdX5tyeLg
r4JNlzny3yQEnS+wMQSBNdbGg1ALfA/d4UDmCI5096YNvJNbomfKoVERuAE/VD1R
efoyxj2b+36Y0KSe1eBnj5mM9MP+xqtosfR+VrejVqRQlWRRi+hl8Ob1nC5eXWFj
daH6RUbwROlrZU1OcohEtRLAy571aCBM3gRGBgxLu+umfN8InXE7R4RVuZpdXuyw
19b0MO9WuGdtKp370MDBEU1t6UE+3GTyhyjwryzRz7W0brprqbo78YpcwG74o0p9
4Q3DSWGOjxQJFN0yv2SICdYxrP7xHFPAMEh3I4t7lRsN0vGDSPQIjEp6RvCgOsct
EEDuG3iwG9ZPvCSMVtRU/1AbMLf1qZhZZbRxVg92Ctkk6tup470op+ZwNveqCv4a
WrN9MylClaLYOfjvzv2XhJ2ojN9No/twKMeCqfOdk+EBsPDlC8E=
=8+H/
-----END PGP SIGNATURE-----

--XKGBaeSHJygJcraFqtFAg4k3MxXFk4tBs--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ebf99712-b9f6-1438-320d-9f25050f3b8a>