Date: Tue, 30 Aug 2011 22:28:11 -0700 From: perryh@pluto.rain.com To: mandree@freebsd.org Cc: freebsd-ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile Message-ID: <4e5dc66b.yG7fFB738rgdzrhe%perryh@pluto.rain.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
Matthias Andree <mandree@freebsd.org> wrote: > I understand that keeping unchanging software can sometimes be > necessary, if you're working around its quirks. > > 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. > > 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= tags. > > I'm not sure if it's feasible for packages (but OBSOLESCENT could > imply "do not package") but for ports it would be possible. +1. This would also address the python 2.4 problem mentioned in another thread. BTW (if it is not already being done) it would be good for the -recursive targets to check for BROKEN, FORBIDDEN, OBSOLESCENT, (others?) in the dependencies _before_ starting the actual work, since the presence of a problematic dependency may well affect the user's decision to install/build/whatever the leaf port.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e5dc66b.yG7fFB738rgdzrhe%perryh>