On Thu, Nov 11, 2004 at 02:59:45PM +0000, Jim Wise wrote:
> 
> Module Name:	src
> Committed By:	jwise
> Date:		Thu Nov 11 14:59:45 UTC 2004
> 
> Modified Files:
> 	src/distrib/sets: TODO
> 
> Log Message:
> Revert previous.  This was discussed at length in 1999 and 2000.
> 
> If we feel we need to revisit this decision, the place to do this is the
> mailing lists, not the TODO document.

[Rather than fight an endless commit war with someone who makes a
virtue out of attempting to stifle discussion, let's take this to
tech-userlevel.  All followups to that mailing list, please. - agc]

And so to the meat of this.

Firstly, perhaps Jim could outline his views of how this will work,
so that we can all be brought up to speed on his views.

However, I believe that things have moved on since 1999, and
pkg_install has grown a -K dir switch, primarily for package views. 
What needs to be discussed is how to pick up the value of the metadata
directory for the desired package collection, be it a package view,
standard overwrite pkg installation, or system packages.  I know that
I don't want to have to think about whether this is a system package,
or what package view I'm in.  I don't want to specify that on the
command line.  I want to specify it once, and then work with that view
or installation.

It may be that a new switch is necessary, although I doubt this.  Does
-X switch PKG_DBDIRs, does it override PKG_DBDIR in the environment,
should we look at SYSPKG_DBDIR instead, should we provide syspkg_*
commands, should we provide syspkg_* aliases in our standard shells,
loads of questions.

I also had an idea about a separate utility which would stuff the
value of PKG_DBDIR and/or SYSPKG_DBDIR into the environment, and which
would be useful for package views as well.  Or pick up this value by
searching the paths for a magic file in the first view directory for
package views - would that be appropriate for system packages?

All feedback gratefully received.

Thanks,
Alistair