Thus spake William Allen Simpson ("WAS> ") sometime Today...

WAS> I suggest ssh be the "poster child".  That is, get the package version
WAS> up to snuff, remove it from the base install, and figure out what needs
WAS> to be done to make more of the game, misc, text, et alia, installs done
WAS> by a single convenient and efficient distribution system.
WAS>
WAS> Someday, maybe there will only be the kernel, base, and etc.tgz files,
WAS> and maybe those will be "meta-" package upgradable, too....

Okay, disclaimer:  This is only my POV, and any opinions in here are
mine, but I'll try not to get too distorted on the way.

WAS> [At other's suggestion, taking this to the tech-pkg list.]

[Noted.]

Now, then.  My understanding of syspkgs was that "base" was going to be a
"meta-pkg" of sorts, and the other smaller pkgs were going to comprise it
and be selectable at installation time.  I don't *think* it makes sense
either to split everything and his mother out of "base" (I just realised I
misread the above as being "having base only consist of the kernel and the
etc files...", but I had to follow through with the thought), nor to have
everything monolithically in "base".

This is probably going to look very Debian-like when it is finished, I'm
guessing, for better or for worse.  Personally, I can think of much worse
scenarios!

By "single convenient and efficient distribution system", I can only
think you mean "do everything with pkg_*".  I'm hoping that one will use
"pkg_* --system" or some such rather than having "syspkg_*" as a separate
toolset.

				--*greywolf;
--
NetBSD: The Power of Code.