Date: Sun, 6 Mar 2011 17:42:02 +0000 From: "b. f." <bf1783@googlemail.com> To: Grzegorz Blach <magik@roorback.net> Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD needs fresh Blood! Message-ID: <AANLkTimnoeF-d0iqtirXvzxN%2BKpYjTtTibiFQydzSgi1@mail.gmail.com> In-Reply-To: <AANLkTi=d5hP-WHPQVJYk9%2B7gXd-3d5j_wgypz7QM2A6X@mail.gmail.com> References: <AANLkTi=d5hP-WHPQVJYk9%2B7gXd-3d5j_wgypz7QM2A6X@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/6/11, b. f. <bf1783@googlemail.com> wrote: ... >> First of all, I think it's difficult to testing ports. ... >> Another possibility is replace ports in disk, but after upgrade tree eg. >> with portsnap I lose my changes, and portmaster want to rebuild these >> ports to stable release. ... > It sounds like you are using the wrong tools. Although portsnap (which > is not best suited for this purpose) has path arguments and an -l flag > that can be used to add or preserve local changes, and both portmaster > and portupgrade have options to ignore certain ports or to substitute > alternative dependencies, you shouldn't have to make use of them. ... >> Merging trees is another huge problem. >> Portshaker do this very well, but after merge I must rebuild INDEX file, >> which takes long time. This should be faster or even shouldn't be >> required (hard to do). I should mention, too, that despite the awkwardness of these tools in this context, others who prefer to use them have found methods to overcome some of the problems that you mention. See, for example: http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/040366.html b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimnoeF-d0iqtirXvzxN%2BKpYjTtTibiFQydzSgi1>