From owner-freebsd-ports@FreeBSD.ORG Fri Feb 26 10:27:45 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from office.hoster.bg (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with SMTP id A6F1B106566B for ; Fri, 26 Feb 2010 10:27:44 +0000 (UTC) (envelope-from roam@ringlet.net) Received: (qmail 1959 invoked by uid 1000); 26 Feb 2010 10:27:43 -0000 Date: Fri, 26 Feb 2010 12:27:43 +0200 From: Peter Pentchev To: freebsd-ports@freebsd.org Message-ID: <20100226102743.GA1388@straylight.m.ringlet.net> References: <20100225211759.01fa3ef2.simpriv@gmail.com> <20100225205859.GG191@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: <20100225205859.GG191@comcast.net> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Bluefish 2.0.0 released! 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: Fri, 26 Feb 2010 10:27:45 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 25, 2010 at 12:59:00PM -0800, Charlie Kester wrote: > On Thu 25 Feb 2010 at 12:17:59 PST simpriv@gmail.com wrote: > >News 2010 - February 15 - Bluefish 2.0.0 released! > > > >I can't find it in the latest ports collection. >=20 > Others have explained how to contact the maintainer of a port, and how > to determine that it has no maintainer. >=20 > But perhaps some expectation-setting is needed here. =20 >=20 > Bluefish 2.0.0 was released a mere ten days ago. Before it will appear > in the ports collection, two things have to happen. >=20 > First the maintainer must modify the port as needed to get it to compile > on FreeBSD. Sometimes that's trivially simple, sometimes it's > diabolically complex. If the port is depended upon by others, for > example, there might be a need to coordinate the update with them. So > it's not unusual for the maintainer's part of the porting process to > take several days or even weeks. That's true - and yes, there are port updates that take weeks sometimes. (although, well, some of *my* updates in the past have been known to take weeks for other reasons, not just the review and technical work) > Second, after the maintainer has submitted a PR with the update, the > committers need to test it. That takes time. Also, judging by what I > can see in the list of currently-open PR's, many committers always have > a dozen or more in process. It's not uncommon (or unreasonable) that > this part of the porting process will take several days or even weeks in > addition to the time the maintainer needed. Well, in this particular case, the maintainer of www/bluefish is a FreeBSD committer himself, so this part might take a bit less time :) But in general, it's true enough. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@space.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 No language can express every thought unambiguously, least of all this one. --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iQIcBAEBCgAGBQJLh6IfAAoJEGUe77AlJ98TaFwP/RDBczWcd6AxkvCXpA1RE/iM tPk8FpYv6rDsBlw8GsTcI5seTQUtFa6E3IOyvm1npK2dZaG37XtVcbQ7B+mqat1v SOUxm54wyYq3KUkchmbdnMh1+uv1fdAQ/l3zNlziEbOWhrFpfwv8L9UI/Gd3/XFP gckyfzfu3Mjr8JVwV+IEv0mHBP/HqvVuq+JbtFE3N7f6ReDNh3o9teKKR35u9INj HkQl5ZJfU6TgrvwLVOFN7lA2oqezPkaaXrF9zgZReEVxSw508T57Rwp0xTR/W4Qk 4m4/7aUcZaOpUx0ahiLrV0InUATXFP74c3l149R0T4F1K4fhyB0WI84pLhY2fHWk VPZwLfx0J0jttHWnGcjT+6UCSBORYlh/Q4Fv7dhja4buSMU5IaP1wD2nMcHHIp18 5A1M5wvTkGz3OuYkWQ9cMrcv2cwYuGXDwTak9JSfXfPwQsDU9JZCxHFj4U+j7teh OquJjHcXC+CfTBV7McFFGLlvBzT7c6mJ5tsUk9ecO48lp7oJhmf0RC0mhMAhZezB NrbEouGPczXRokP83r85VMIEsBtx7tdAM1mNVmhg4H2NbOWuSUAWhGY80kz3O6Uj PNoYaZuKtnJ5/uwcCrVE3MgtTBqW+7GOlmEwpDI7gE3cSF9QtdzNI7EBT0A1RvBN im1nmm5S1Hya8gwb+jj5 =Madn -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1--