On Fri, 2 Dec 2005, iMil wrote:
> i am working on a pkg_select extension that Alistair requested: giving the
> tool the possibility to work with a binary packages directory only, without 
> any pkgsrc hierarchy.

Good thing - thanks for picking the work on pkg_select up again, and sorry 
for sort of dropping that ball!


> The extension is almost finished but i'd like to ask a simple variable
> naming question. Right now i have arbitrary chosen ${BINPKGDIR} not
> to conflict with any other tool, do you mind if if use ${PACKAGES} as the 
> binary packages location ?

PACKAGES sounds good, for the local directory that has the "All" dir and 
the category dirs - it's what pkgsrc uses.

Is this in as environment variable?
I wonder about consequences when setting this, finding a pkg doesn't 
build and the someone uses pkg_select to build a pkg from pkgsrc - that 
may lead to undesired results.

If this is to denote a read-only or remote site, maybe better evaluate 
BINPKG_SITE, which is used by pkgsrc. See BINPKG_SITES, BIN_INSTALL_FLAGS 
and the bin-install target in packages(7) and pkgsrc/mk.

Not sure where to go, honestly.


  - Hubert