On Fri, 19 Apr 2002, Luke Mewburn wrote:

> 	+ the majority of our users just install packages with default
> 	  settings (into /usr/pkg).  I assume that they would prefer to
> 	  have a consistent location for configuration (/etc/rc.conf,
> 	  /etc/rc.conf.d/foo), and a consistent location for rc.d
> 	  scripts for manual startup (/etc/rc.d).  As an end user, it
> 	  would annoy me to no end to remember to type /etc/rc.d/foo
> 	  for "base NetBSD" scripts, /etc/rc.pkg.d/bar for package items,
> 	  /usr/local/etc/rc.d/baz for my stuff, ...

One of the things I think we were trying to support w/ syspkgs was having
a split root and user. As I understand it any given subset is divided up
into different packages for different mount points.

By moving all of the config files and scripts to /etc, we split packages
between root and /usr/pkg parts; we go against what we're trying to do w/
syspkgs. What can we do to support having a split / and /usr/pkg?

I can think of some things, but they are kinda cheezy; install files in
/usr/pkg/etc/XXX, and have a tool (run automaticallyy during pkg_add
perhaps) copy them to /etc. Or having a step in the startup where we have
rcorder rescan (presumably after /usr and /usr/pkg have been mounted), and
add newly-found scripts. Obviously in the latter case, if a new script is
found to have wanted to run before something that's already run, well, it
looses.

Thougths?

Take care,

Bill