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?
> 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?
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
