[bug-notifications] [alternatives 0004560]: /opt/csw/sbin/alternatives not installed in sparse zone

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4560 
====================================================================== 
Reported By:                holzi
Assigned To:                phil
====================================================================== 
Project:                    alternatives
Issue ID:                   4560
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2010-10-01 16:13 CEST
Last Modified:              2010-10-02 19:41 CEST
====================================================================== 
Summary:                    /opt/csw/sbin/alternatives not installed in sparse
zone
Description: 
I have CSWsudo installed in globle zone. Hence alternatives too.
If I create a sparse zone alternatives is not installed correct into the
sparse zone. Hence no symlinks for sudo.

pkgchk CSWalternatives              
ERROR: /opt/csw/sbin/alternatives
    pathname does not exist

The script is missing.
====================================================================== 

---------------------------------------------------------------------- 
 (0008323) phil (manager) - 2010-10-02 19:41
 https://www.opencsw.org/mantis/view.php?id=4560#c8323 
---------------------------------------------------------------------- 
It already is documented on our website. 
If you have a suggestion on a specific location where an additional
reference would be appropriate, please let us know.

As documented on the page I referenced above, your mixed use of pkgadd is
a violation of basis consistency at the sysadmin level.
If you are "inheriting packages from the global zone", then you should
mark the relevant directories as "inherit-pkg-dir". That's what it's for.

If you want to install packages locally for a directory... then great!
Install packages locally only, for that directory in that zone.

Just dont mix and match. Pick one strategy and be consistent about it, for
that zone. Then these problems wont come up.

I will also point out, that this is not a bug in "our" packages. This is
an annoyance of how pkgadd works in Solaris, when you do global pkgadds.
I'm not refusing to fix a bug in our package - I'm just informing you
about how Solaris works.
If you disagree with these statements, I welcome you to make a technical
level comment on how specifically we can "fix" this issue.