Alexey Dokuchaev <[email protected]> wrote: > On Wed, Sep 29, 2010 at 09:00:06AM +0200, Erwin Lansing wrote: > > This case is actually actively taken care of, although of course > > some cases will fall through the cracks. Portmgr does > > occassionally run a full build of all ports on the pointyhat > > cluster with local caching turned off, forcing all ports to be > > fetch from the configured MASTER_SITES. In fact, I started one > > just yesterday. Maintainers will be informed and unmaintained > > ports will be marked BROKEN, and lateron scheduled for deletion. > > But like you said, there will still be cases that will fall through > > and we do need to get better at removing stale ports. > > I think people would also appreciate more clear criteria on when to > mark port as deprecated. For now the only one I know is "being > broken and unmaintained for 6-12 months". Availability of distfile > and master site does not seem enough. Unpatched security issue, on > contrary, could encourage deprecation with shorter expiration period.
Just a thought. How about setup a public database which tracks how long a port is unmaintained/unupdated. Review the ports which should have a maintainer since they are somewhat important. Automatically expire ports that didn't have a maintainer for let's say a year. Emanuel _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[email protected]"
