Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Aug 2011 09:34:33 -0700
From:      Chip Camden <sterling@camdensoftware.com>
To:        freebsd-ports@freebsd.org
Subject:   Re: cvs commit: ports/mail/procmail Makefile
Message-ID:  <20110830163433.GC34744@libertas.local.camdensoftware.com>
In-Reply-To: <4E5D0856.8080505@FreeBSD.org>
References:  <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org>

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

--raC6veAxrt5nqIoY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Quoth Matthias Andree on Tuesday, 30 August 2011:
> Am 30.08.2011 14:27, schrieb Kurt Jaeger:
> > [maildrop]
> >>> - Can it use the 700+ lines long .procmailrc I have running
> >>>   in a criticial application or do I have to migrate that ?
> >>
> >> You'd have to migrate that.
> >=20
> > That's what I assumed.
> >=20
> >> Bottom line: the sooner we get rid from procmail the better.
> >=20
> > There are many other applications that have issues, as well.
> >=20
> > It's already a lot of work just to keep up with the bug-de-jour
> > and the upgrade-de-jour and doing it all in parallel does
> > not scale very well.
> >=20
> > Therefore, one has to choose what one can work on.
> >=20
> > If the fbsd ports drop procmail, it will just add more on
> > my plate that I have to do myself. Similar to many other
> > apps and ports and you-name-it.
> >=20
> > While I dislike bitrot like anyone else, I have an issue with
> > the dropping of ports in general, because that will not scale.
>=20
> I understand that keeping unchanging software can sometimes be
> necessary, if you're working around its quirks.
>=20
> At the same time I'd like to discourage new installations of dead
> software so that it disappears over time, rather than haunt fresh systems.
>=20
>=20
> How about if we added a new tag "OBSOLESCENT" or so that permits
> building the software only if it's already installed but refuses new
> installations?  Of course there could be a switch to override that, like
> TRYBROKEN that can override BROKEN=3D tags.
>=20
> I'm not sure if it's feasible for packages (but OBSOLESCENT could imply
> "do not package") but for ports it would be possible.

I like this idea.  But please call it OBSOLETE, instead of OBSOLESCENT.
Gratuitous suffixes are as much of a bane to the language as obsolete
software is to an OS.

--=20
=2EO. | Sterling (Chip) Camden      | http://camdensoftware.com
=2E.O | sterling@camdensoftware.com | http://chipsquips.com
OOO | 2048R/D6DBAF91              | http://chipstips.com

--raC6veAxrt5nqIoY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)

iQEcBAEBAgAGBQJOXREZAAoJEIpckszW26+RgGIH/i2hZqIiomNlu+4Bff0vYuCK
wpMew8hbg89M11X5IH1hcNbWUWIfSU0uW5IblXL9PRf+Vv3xcNTYkJrIKrUBYKoN
RcFQ0Fj0vPK/u7rjsTsvhUgaMJ2B5yKnggcSYk4FPa0J/c/GO84J0Q5IAyOsNVzE
hUx1JdR0ZI+uy9gccTV0Sv2HFanFNRlz5Y1CkrKUTkO7YOxfe1lxdIdevHSAziC7
JO0xpFm2u+a/AifV1pqP1seHNlwhbZTVFcWAKNoI/OJR7JKP1AN9/mQlAG3z10bc
y+MH4He36DzKdoCY0mXBSIB2Gw+nX+9DyI8G3iYP98qTwwLPoNCfx4P9eJGuReE=
=dSbo
-----END PGP SIGNATURE-----

--raC6veAxrt5nqIoY--



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