J. Estes writes:
> I understand the need for http/https support in pkgadd, but the
> argument that static linking leads to multiple copies of software
> also occurs with dynamic linking, with bad results. As an example,
> the pkgadd in Solaris 10 is dependent specifically on version
> libopenssl.
J. Estes wrote:
This is the crux of the current problem with Solaris 10:
the /usr/sfw components are not optional. They are
loaded without the user having any choice in the matter.
You're not forced to use them for your own software; put
your libraries in /usr/local/lib or /opt/xxx and
J. Estes wrote:
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 Coopersmi
> 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.
>
>
