Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Oct 2006 12:03:17 -0500
From:      linimon@lonesome.com (Mark Linimon)
To:        Peter Thoenen <eol1@yahoo.com>
Cc:        ports@freebsd.org
Subject:   Re: Port Bloat
Message-ID:  <20061015170317.GA17926@soaustin.net>
In-Reply-To: <20061015055332.82539.qmail@web51905.mail.yahoo.com>
References:  <20061015055332.82539.qmail@web51905.mail.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 14, 2006 at 10:53:32PM -0700, Peter Thoenen wrote:
> B) In line with A, has anybody thought about just marking ALL
> ports@freebsd.org as scheduled for deletion on X date.

It turns out that a few of them are key pieces of infrastructure.  Perhaps
we can generate a list of "ports that we would really like to see adopted."

It has also turned out, in the past, that "one man's trash is another man's
treasure" as the old saying goes.  When we first instituted the DEPRECATED/
EXPIRATION_DATE process, a lot of people did indeed adopt some ports in a
flurry of activity, but there was a fair amount of fuss generated, too.
Since then, several hundred stale/dead ports have indeed been pruned.

Unfortunately we don't really have any good proxy for "what ports are in
use".  The closest we have is FreshPorts subscriptions, which, the last
we checked, showed that several thousand ports were not being tracked by
anyone who subscribed.  Unfortunately the sample space for FreshPorts is
self-selecting so it can't be taken as authoritative.  I advocate that
people subscribe to FreshPorts and list the ports they use so that we can
better judge this.

One of my eventual goals for portsmon is to include "date of last commit"
(as well as the fetch survey results) to try to generate another proxy for
this.  I don't have any other ideas that wouldn't just create a bunch of
controversy, however.

mcl



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