--- On Sat, 1/30/10, Mark Peoples <[email protected]> wrote:
> From: Mark Peoples <[email protected]> > Subject: $PKG_PATH with multiple sites > To: [email protected] > Date: Saturday, January 30, 2010, 4:54 PM > I set my $PKG_PATH like: > > PKG_PATH=/localnet/nfs/server:ftp://ftp3.usa./ftp/path/as/usual... > > From pkg_add(1), my impression was if I did something like > > pkg_add a-package-not-in-the-nfs-path-above > > it would first look in the nfs path above, and, if it > doesn't find it, it would then go look at the ftp site. is > that the intended behavior? because that's how i interpret > pkg_add(1), but it's not > > if that's not the intended behavior, does anyone have any > pointers on how to make it work that way? > > this is on about a 4 day old -current, but it's been not > working the way i've thought it should for some time > > thanks! > > --- On Sat, 1/30/10, Mark Peoples <[email protected]> wrote: > I set my $PKG_PATH like: > > PKG_PATH=/localnet/nfs/server:ftp://ftp3.usa./ftp/path/as/usual... > >From the pkg_add man page of OBSD 4.3 PKG_PATH If a given package name cannot be found, the directories named by PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name, ending in a slash. ....... In the man pages of the newer OBSD releases this "Each entry consists of a directory name, ending in a slash." phrase has disappeared. But I still use that terminating slash, which used to be mandatory. =Adriaan=
