> You're not forced to use them for your own software;
> put your libraries in /usr/local/lib or /opt/xxx and link
> with that.
>
> - Bart
I normaly do exactly that. But that still leaves the user with 481 MB of bloat
in /usr/sfw , most of which is not required by the core O/S. This does not
> You can install whatever bits you want for your
> applications to use; you need only configure your
> apps to link against your versions of those libraries.
>
> Get used to sedimentation; Solaris over time will
> contain more and more pieces who originate outside of Sun
> Microsystems, Inc.
I
> Where do you draw the line between part of the OS and
> a third party library? What are sendmail, bind, Xorg, libX11? A
> very large amount of Solaris has origins outside Sun - whether
> that be from BSD, AT&T, or one of the many open source projects
> included.
>
> --
> -Alan Coopersmith
> The reason they are required is that pkgadd natively
> supports installing software via http: and https: with the "-d
> device" option. You can download and install signed
> packages over the web. This is part of the functionality
> required by the existing Solaris 10 "WAN boot" feature.
>
>
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
I have been using Sun Solaris (2.5.1 up to 8) without having the core O/S
dependent on /usr/sfw software. It is a detraction that should be removed, or
at least the user should be allowed to choose to completely preclude its
installation. This is especially true of the dependencies on pkgadd/p
