On Sat, Jun 10, 2006 at 10:28:54AM -0400, Eric d'Alibut wrote:
> Hi. Instead of plunging into tracking -current, this time around I
> have gotten in sync with netbsd-3-0. The aim is to get experience with
> maintaining a stable production machine.
> 
> Should I set my PKG_PATH for binary pkgsrc packages to one of the
> quarterly collections, rather than simply to '3.0'? e.g:
> 
> setenv PKG_PATH
> ftp://ftp.netbsd.org/pub/NetBSD/packages/packages-2006Q1/NetBSD-3.0/i386/All
> 
> I'm a tad confused as to the relationship between release branches and
> pkgsrc. My thought is to avoid a binary pkgsrc collection that is
> basically a creature of -current.

ftp://ftp.netbsd.org/pub/NetBSD/packages/3.0/i386 will point to the
last build of the last stable branch for 3.0/i386. So right now
3.0/i386 points to packages-2006Q1/NetBSD-3.0/i386, it will be changed
to point to packages-2006Q2/NetBSD-3.0/i386 when binaries for packages-2006Q2
are available.
Choosing one or the other depend on your policy. Using packages/3.0/i386
you don't have to track branch tags and annouce to know when a new binary set
is availble, but you can end up mixing binaries from different branchs which
can cause troubles (you may have to update a lot of dependancies before
being able to install a package). using packages-2006Q1/NetBSD-3.0/i386 you
avoid that, and you can switch to the next branch when *you* choose.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--