Hi

We have an appliation that installs *one* file into /usr/man. The
application is hosted in a Solaris 10 U3 zone. Because of the
one file the zone is installed as whole-root model (before I
was involved!). I'd much rather have the option to run with
a sparse-root model, and in particular I would rather make that
decision on a more compelling reason than one man page.

If I was doing it I would have at least faked it out somehow, and
just put the file in the right place from the global zone.

However, I wouldn't want to recommend that as a good solution. I'd
rather have a more defensible solution.

One that I have considered is to not have /usr as an inherit-pkg-dir
directory and instead have each directory subordinate to /usr
(/usr/bin /usr/lib etc etc) individually defined as inherit-pkg-dir,
leaving out /usr/man.

The issue I see with this is that one *doesn't* define /usr as
inherit-pkg-dir - it's a default that is not in the config file.
Is choosing a sparse-root model an all-or-nothing choice in
respect of those default dirs?

Does anyone have any other ideas?

Cheers, Liam