Date: Mon, 13 Sep 2010 17:38:04 -0700 From: Stanislav Sedov <stas@FreeBSD.org> To: "Philip M. Gollucci" <pgollucci@p6m7g8.com> Cc: ruby@freebsd.org, FreeBSD Port Management Team <portmgr@freebsd.org> Subject: Re: portupgrade Message-ID: <20100913173804.d4aa5eb9.stas@FreeBSD.org> In-Reply-To: <4C8EB9BC.4020208@p6m7g8.com> References: <4C8EB9BC.4020208@p6m7g8.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Mon__13_Sep_2010_17_38_04_-0700_jijMM04ARKMRIdiB Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 13 Sep 2010 23:54:36 +0000 "Philip M. Gollucci" <pgollucci@p6m7g8.com> mentioned: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > All, >=20 > 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. >=20 > I've also dropped 1.8.6 ruby support from the comments. >=20 > I assigned all 29 ports PRs relating to the 2 of them to myself. >=20 > The 1st thing I want to do is suggest that we update > ports-mgmt/portupgrade to ports-mgmt/portupgrade-devel and rmport the > latter. >=20 > 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. >=20 > That should leave the prs without patches. And we'll deal with that then. >=20 > 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. >=20 > What we should really do is figure out how to consolidate to portmaster > since that is *very* well maintained and drop this time suck. >=20 > P.S. > No offense to the authors, I used portupgrade for quite sometime > successfully before switching to my Tinderbox setup. >=20 Philip, there's a branch in projects/ we use for developing pkgtools. This place is exactly where portupgrade-devel comes from. Feel free to submit your patches/echancements. But, please, do not commit PRs blindly, most of them require a lot of thought and work. I committed all the low-hanging fruit before. Saying this, I'm absolutely against passing the port to ports@. The reason it's assigned on ruby@ and not ports@ is that we don't want random people committing to this port thus possibly destabilizing the important tool. --=20 Stanislav Sedov ST4096-RIPE --Signature=_Mon__13_Sep_2010_17_38_04_-0700_jijMM04ARKMRIdiB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJMjsPwAAoJEL8lojEJL9nwkvMQALJnLAv6a5RI6JAyTMJGdXTW SUhmIDDK25sp9Csw9n9PFwU4OyMxfY+lklhTu65gesl5h53D8Ji4kjeYWE8BxMmk fEggT+QFQdmP7zBh1cQo9fj71NE9qZ7Zoq1mtvkU9OXHq/FZFySgLfFy3UksfkYt OgSrTW7BIpdhoqbPd6sARM2j09PLotV+6Y4ShJzI/sLcgghV3JD+svMgwKBut5V+ UKs90NR7ocmH4o2C5k+ai4nipgJSlXc0bG9RSxPkrDzaVBJzKdsyuGU9v9pD/2nH eF5HGfuwC9x/fUG59uryOUO5G8TOz0PW8K7unM+7tYGwjrmmvQl5o8ShB4Haq66z vyj2sV9v4ac6u19bR46YG0YSEEfK2sK4jlhbA8IFs7ePPhao3HU/glRuCjAb1rkJ YfhSujtV1Z/3V7E/EN5MG9u7qDVQqL8cyD32aWa6Dcsijika3j0MBwJ7IuzZgkG+ U5eLhwKa2/mhHCZZFyNLJ8mxA7C/mtzXvxRpG65yjSCuVBcXpJHd1yAa8+89j8wm SX6WvDn2+VAl17I8z+nh3X3MVlAemzQpB/zkBHqQxaSsZsAOxhfwhF0G2dodaGzg HH35NDqqCTAQgRDNWsaxrSz32HFR7F+hKNohuYwbnhooYWmtjtciZPhqH+WBVcCU 1oU1KbfyZStxDr5N/jr5 =T8ig -----END PGP SIGNATURE----- --Signature=_Mon__13_Sep_2010_17_38_04_-0700_jijMM04ARKMRIdiB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100913173804.d4aa5eb9.stas>