Rainer Orth wrote:
> Douglas,
>
>> I misnamed this ARC case, and it appears to be causing a significant
>> amount of confusion. This case should have been named Bundled Compiler
>> Collection. The intent is to bundle Sun compilers into /usr. We are
>> not bundling all of Sun Studio. This collection only contains C
>> and C++ compilers along with their debugger, dbx.
>
> ok, but where's the benefit of doing so, both for the users/developers and
> the DevPro team?
The next version of the ARC case will say this:
3.3. Business Justification:
Encourage FOSS inclusion into OpenSolaris repositories by
minimizing compiler-related porting effort.
Provide a bundled set of compilers for any distribution of Solaris.
The target customers are people building software on Solaris
Nevada derived distributions. Not necessarily people building
Solaris itself. The culture of Nevada is for consolidations to
deliver the latest semi-stable development builds, which are
periodically updated. This closely matches the Sun Studio
Express release cycle.
>
>> Given the design of the Sun compilers, we can not just install them
>> into /usr/bin, /usr/lib, etc. without significant redesign. We need a
>> location into which to install the compiler components, with symlinks
>> to those components in /usr/bin and /usr/share/man. So our original
>> intent was to install the bundled compiler collection components into
>> /usr/compilers/{bin,lib,...}, with symlinks in /usr/bin and
>> /usr/share/man. We chose the name 'compilers' to intentionally
>> indicate these are the default|builtin|preferred|bundled compilers.
>> There would not be multiple versions, there would always and only be
>> one set of bundled compilers. Versions of the unbundled Sun Studio
>> will continue to install into /opt, i.e. /opt/sunstudio13,
>> /opt/sunstudio14, etc.
>
> There's no problem here, on the contrary I consider it a benefit that/if
> the installation supports the installation of several different versions in
> parallel, only designating one as the default (this should be the latest
> stable release in my opinion), but giving developers the opportunity to
> easily use either an earlier release should the need to for some reason, or
> test Studio Express if they desire. The architecture seems to be in place
> to handle all this, so why not go the whole way?
The unbundled Sun Studio also provides an optional package for
installing links in /usr/bin and /usr/share/man, these override the
links of this bundled compiler as it does the links of any other
installed versions of Sun Studio. We believe this does give developers
the opportunity to easily use any version of Sun Studio.
As to why not bundle all of Sun Studio so it is available in any distribution
of Solaris, that is a marketing decision or opportunity for which I do not have
an explanation.
>
> Rainer
>
> -----------------------------------------------------------------------------
> Rainer Orth, Faculty of Technology, Bielefeld University
