Date: Mon, 13 Sep 2010 23:54:36 +0000 From: "Philip M. Gollucci" <pgollucci@p6m7g8.com> To: ruby@freebsd.org Cc: FreeBSD Port Management Team <portmgr@freebsd.org> Subject: portupgrade Message-ID: <4C8EB9BC.4020208@p6m7g8.com>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All, I've created http://svn.freebsd.org/base/user/pgollucci/portupgrade/ w/ trunk, branches, tags. I've imported 2.4.6 (ports-mgmt/portupgrade) and 20091221 (ports-mgmt/portupgrade-devel) in. I've tagged them. I've also dropped 1.8.6 ruby support from the comments. I assigned all 29 ports PRs relating to the 2 of them to myself. The 1st thing I want to do is suggest that we update ports-mgmt/portupgrade to ports-mgmt/portupgrade-devel and rmport the latter. Once that happens I'll start looking through the PRs and applying the ones with patches. I should then be able to present a 2.5.0 test candidate. Once tested we'll update the port. That should leave the prs without patches. And we'll deal with that then. Having said all this, I've absolutely 0 desire to maintain portupgrade. Once we get this far, unless I'm out-right veto'd I'm going to reset MAINTAINER from ruby@ to ports@. If someone does veto me, I'll ask portmgr@ to support b/c I know its not being cared for with ruby@ which is all of 4 people. What we should really do is figure out how to consolidate to portmaster since that is *very* well maintained and drop this time suck. P.S. No offense to the authors, I used portupgrade for quite sometime successfully before switching to my Tinderbox setup. - -- - ------------------------------------------------------------------------ 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer, FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iD8DBQFMjrm8dbiP+9ubjBwRAsQPAKCLhnU6kyppo6vYgoHCHq+hyfInNgCfXjXr tDGRrmcqE+pW8LEP5UJiyAs= =UWtM -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C8EB9BC.4020208>