Date: Wed, 9 Mar 2011 21:13:53 +0100 From: Grzegorz Blach <magik@roorback.net> To: Warren Block <wblock@wonkity.com> Cc: Michel Talon <talon@lpthe.jussieu.fr>, freebsd-ports@freebsd.org Subject: Re: FreeBSD needs fresh Blood! Message-ID: <AANLkTin_tkUDB4nq2EpajbLyms2BPvWq8B2f%2B7LO%2BFg5@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1103081008470.41038@wonkity.com> References: <20110308162439.GA98584@lpthe.jussieu.fr> <alpine.BSF.2.00.1103080941340.10045@wonkity.com> <alpine.BSF.2.00.1103081008470.41038@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 8, 2011 at 18:13, Warren Block <wblock@wonkity.com> wrote: > On Tue, 8 Mar 2011, Warren Block wrote: >> >> On Tue, 8 Mar 2011, Michel Talon wrote: > >>> My experience is that all FreeBSD ports tools are incredibly slow, be it >>> portupgrade, portmaster, even the basic tools like pkg_version. Maybe it >>> would help to recognize that such observations are perhaps not unrelated to >>> the original poster comments. >> >> I don't understand what you mean by that last sentence. OP was talking >> about the difficulty of using or merging alternate ports trees, AFAIR. Sorry >> about the topic drift; we can start a new thread if appropriate. > > And of course now I see it: the OP also mentioned the delay in rebuilding > INDEX after merging ports trees. > > That was a problem back before the ports cluster built INDEX files for > download, and there were Perl and other implementations that could rebuild a > local index faster than the stock ports implementation. Can't recall > exactly what they were. If still applicable, integrating those faster > methods into the ports system would be a solid improvement. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > Building INDEX is not essential in this thread, merging trees is closer to subject, but primary I want, that testing development version of ports will be simpler. Please look at: 'Firefox 4 - Beta' threat: http://lists.freebsd.org/pipermail/freebsd-ports/2011-March/066353.html some people don't known where they can find freebsd-gecko development repo. Or at 'xorg-server 1.9.3 and 1.10.0' threat: http://lists.freebsd.org/pipermail/freebsd-ports/2011-March/066421.html Martin wrote: > I'll cleanup all the mess and commit all stuff to the xorg-dev repo. Maybe > someone have intressing to test it. but without any info where I can find xorg-dev repo, How I can test new xorg, since I don't known where this repo is?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin_tkUDB4nq2EpajbLyms2BPvWq8B2f%2B7LO%2BFg5>