From owner-freebsd-ports@FreeBSD.ORG Mon Jul 25 19:15:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EDAF1065670; Mon, 25 Jul 2011 19:15:02 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from bsdevel2.freebsdnorth.com (unknown [IPv6:2001:470:7:d77::2]) by mx1.freebsd.org (Postfix) with ESMTP id 698CD8FC14; Mon, 25 Jul 2011 19:15:02 +0000 (UTC) Received: from maximum3.maximumdata.biz (akbeech-2-pt.tunnel.tserv14.sea1.ipv6.he.net [IPv6:2001:470:a:2e9::2]) by bsdevel2.freebsdnorth.com (Postfix) with ESMTP id 878E2C3A9D; Mon, 25 Jul 2011 18:52:26 +0000 (UTC) From: Beech Rintoul Organization: FreeBSD To: freebsd-ports@freebsd.org, Eitan Adler Date: Mon, 25 Jul 2011 11:14:59 -0800 User-Agent: KMail/1.13.7 (FreeBSD/9.0-CURRENT; KDE/4.6.5; i386; ; ) References: <4E2CD52C.8060701@FreeBSD.org> In-Reply-To: <4E2CD52C.8060701@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart14449526.3VmDjgMDct"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201107251115.00049.beech@freebsd.org> Cc: ruby@freebsd.org Subject: Re: Time to mark portupgrade deprecated? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 19:15:02 -0000 --nextPart14449526.3VmDjgMDct Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 24 July 2011 18:30:04 Steve Wills wrote: > On 07/24/11 22:20, Eitan Adler wrote: > > At this point noone is maintaining portupgrade any more and a large > > number of PRs have been filed against it (see > > http://www.freebsd.org/cgi/query-pr-summary.cgi?text=3Dportupgrade). No > > one has stepped up to do the work to fix these bugs so it is time to > > officially drop it. >=20 > Personally, I agree it's time to drop it if no one is going to do the > work to maintain it, which at this point it seems clear is not going to > happen. I'd be happy to be proven wrong about that. >=20 > So the question becomes, how do we go about doing it? First step would > be changing the handbook. Most UPDATING entries seem to include both > portupgrade and portmaster instructions these days, so that should be > covered. The next issue would be warning portupgrade users, perhaps by > marking the port DEPRECATED? I'd think a date a little longer than the > usual month would be needed before expiring. Why pick portupgrade when a lot of people (including myself) use it? There = are=20 probably 100's of ports more worthy of deprecation. Maybe there should be a= =20 policy to deprecate all unmaintained ports if nobody steps up. You can alwa= ys=20 drag it out of the attic if enough people squak and probably find someone t= o=20 maintain it in the process. Just my .02 Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html =2D------------------------------------------------------------------------= =2D------------- --nextPart14449526.3VmDjgMDct Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iF4EABEIAAYFAk4twLMACgkQQLNZXRF1OntdJAD+OFWd6E7MaBtGrB2J7W0fHdyM lG1r6m0AujxayPIe7OsBAI8IP8PtFDP8JDDpiRWiVjiLuAzpZFZacxpsBM8WP+uN =dwpV -----END PGP SIGNATURE----- --nextPart14449526.3VmDjgMDct--