On 4 Jun 2003 07:25:01 -0500, Martin Schmitz wrote:
> Richard Rauch <rkr@olib.org> writes:
> 
>> My approach is to, at wide-spaced intervals, get the latest pkgsrc and
>> then try to stick with that version for as long as I can.
> 
> Thanks, I guess this is what I wanted to hear. ;-)
> If I would do a fresh install of NetBSD I would stay with the pkgsrc
> coming with it for as long as it is possible. But as I already installed
> a new one from current I keep on going with it for as long as I don't
> find any serious bugs in it.

If you support a large number of packages or the larger meta-packages
and want to stay relatively current, I would recommend taking a
look at building binary packages using pkg_comp/pkg_chk and then
installing the binary packages in your production environment once
you have them all built correctly.

Sometimes it can take a week or so to get pkg build problems solved
and it's nice to get to try until it works without trashing your
production environment.

One of our dual-cpu Athlons is pretty much dedicated to building
releases and a set of packages for -current and 1.6.1, and it stays
mostly busy with those attempts. Need a more automated way to do
it though.