> > More seriously -- creating a metapackage is indeed non-obvious.  I
> > just built one (not yet committed -- there are still some issues) and
> > it took several tries and checks of how existing metapackages work.
> 
> That sounds not only strange but ominous... I've always thought about 
> meta-package as a sort of pkg_add runing against a file with package 
> names in it. Nothing more. Dependencies were to be downloaded 
> automatically as usual.

Okay, I don't see any examples of meta-packages with configurations.

So create multiple packages: a custom configuration/themes package and a 
meta-package that pulls that custom package in plus all the other packages 
for your ready-to-use solution.



  Jeremy C. Reed