From owner-cvs-all@FreeBSD.ORG Wed Sep 29 07:00:08 2010 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F7EC1065670; Wed, 29 Sep 2010 07:00:08 +0000 (UTC) (envelope-from erwin@mail.droso.net) Received: from mail.droso.net (koala.droso.net [IPv6:2001:6c8:130:400::6]) by mx1.freebsd.org (Postfix) with ESMTP id B661E8FC0A; Wed, 29 Sep 2010 07:00:07 +0000 (UTC) Received: by mail.droso.net (Postfix, from userid 1001) id 3993C1CC60; Wed, 29 Sep 2010 09:00:06 +0200 (CEST) Date: Wed, 29 Sep 2010 09:00:06 +0200 From: Erwin Lansing To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org Message-ID: <20100929070005.GU77643@droso.net> References: <201009272151.o8RLpA8I002279@repoman.freebsd.org> <20100928024255.GA61304@FreeBSD.org> <20100928075649.c3bcb0a9.ehaupt@FreeBSD.org> <20100928122336.GB32589@FreeBSD.org> <4CA269E6.4030005@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BZziOT8Kz25R/m/E" Content-Disposition: inline In-Reply-To: <4CA269E6.4030005@FreeBSD.org> X-Operating-System: FreeBSD/i386 7.3-STABLE User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Re: cvs commit: ports/sysutils/screenie Makefile pkg-descr X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: **OBSOLETE** CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2010 07:00:08 -0000 --BZziOT8Kz25R/m/E Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 28, 2010 at 03:19:18PM -0700, Doug Barton wrote: > That concern is understandable, but the problems come in down the road=20 > when something in the infrastructure changes, and there is no one to=20 > update the stale port. Not culling stale stuff is also how you get into= =20 > situations like I cleaned up recently where you have ports that haven't= =20 > even been fetchable for years still sitting around because no one pays=20 > attention to them. >=20 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. -erwin --=20 Erwin Lansing http://droso.org Prediction is very difficult especially about the future erwin@FreeBSD.org --BZziOT8Kz25R/m/E Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iD8DBQFMouP1qy9aWxUlaZARAlabAKDiefNu3NmCTOGxdkMFTsKjaXav1ACglK3K 1AcY8jy2qwat3BpzU15rXjc= =ZAtx -----END PGP SIGNATURE----- --BZziOT8Kz25R/m/E--