Re: Bluefish 2.0.0 released!
On Thu, Feb 25, 2010 at 12:59:00PM -0800, Charlie Kester wrote: On Thu 25 Feb 2010 at 12:17:59 PST simp...@gmail.com wrote: News 2010 - February 15 - Bluefish 2.0.0 released! I can't find it in the latest ports collection. Others have explained how to contact the maintainer of a port, and how to determine that it has no maintainer. But perhaps some expectation-setting is needed here. Bluefish 2.0.0 was released a mere ten days ago. Before it will appear in the ports collection, two things have to happen. 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 -- Peter Pentchev r...@ringlet.netr...@space.bgr...@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. pgplNcg82tj9f.pgp Description: PGP signature
Bluefish 2.0.0 released!
News 2010 - February 15 - Bluefish 2.0.0 released! I can't find it in the latest ports collection. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Bluefish 2.0.0 released!
On Thu, Feb 25, 2010 at 09:17:59PM +0100, simp...@gmail.com wrote: News 2010 - February 15 - Bluefish 2.0.0 released! I can't find it in the latest ports collection. You're better off contacting the maintainer (sylvio@), unless the maintainer is po...@freebsd.org (this mailing list). If the port is maintained by po...@freebsd.org then it is effectively unmaintained and you should look into adopting and updating it yourself. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Bluefish 2.0.0 released!
On Thu, 2010-02-25 at 21:17 +0100, simp...@gmail.com wrote: News 2010 - February 15 - Bluefish 2.0.0 released! I can't find it in the latest ports collection. how about. ports/www/bluefish and notify the maintainer and ask if he wants to update it? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Bluefish 2.0.0 released!
On Thu 25 Feb 2010 at 12:17:59 PST simp...@gmail.com wrote: News 2010 - February 15 - Bluefish 2.0.0 released! I can't find it in the latest ports collection. Others have explained how to contact the maintainer of a port, and how to determine that it has no maintainer. But perhaps some expectation-setting is needed here. Bluefish 2.0.0 was released a mere ten days ago. Before it will appear in the ports collection, two things have to happen. 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. 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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
