As the previous message indicated more and more software in Solaris was
developed outside Sun and thankfully they realised that this software needs to
be include as part of the Solaris O/S. Having more and more software built
into the core O/S is good, since I am sure we all remember times we t
J. Estes wrote:
I would have them be completely divorced from the core O/S,
such that core utilities like pkgadd/pkgrm are not dependent
on 3rd party software, such as libopenssl.so, nor libgcc_s.so.
Both /opt/sfw _and_ /usr/sfw should be configurable to be not
installed at all, if the person i
James Carlson wrote:
The design issue is how to have a feature like this ("optional"
web-based package install) without making pkgadd depend directly on
the OpenSSL libraries. I think that there's room for useful work in
this area. It may be possible to decouple these two components in
such a w
J. Estes wrote:
I would have them be completely divorced from the core O/S, such that core
utilities like pkgadd/pkgrm are not dependent on 3rd party software, such as
libopenssl.so, nor libgcc_s.so.
Where do you draw the line between part of the OS and a third party
library? What are sendm
J. Estes writes:
> I would have them be completely divorced from the core O/S, such
> that core utilities like pkgadd/pkgrm are not dependent on 3rd party
> software, such as libopenssl.so, nor libgcc_s.so. Both /opt/sfw
> _and_ /usr/sfw should be configurable to be not installed at all, if
> the
I would have them be completely divorced from the core O/S, such that core
utilities like pkgadd/pkgrm are not dependent on 3rd party software, such as
libopenssl.so, nor libgcc_s.so. Both /opt/sfw _and_ /usr/sfw should be
configurable to be not installed at all, if the person installing it so
