Raj Prakash <Raj.Prakash at sun.com> writes:
> 4. Technical Description:
> 4.1. Details:
> - Existing C, C++ and dbx components of Sun Studio Express
> 2008.11 release will be installed in
> /usr/compilers/suncc2008.11 similar to LSARC/2008/776 GNU
> Developer Collection
I've the same objections here as I've raised for LSARC/2008/776 (many of
which haven't been answered yet):
* Where's the need (or precedent) for the deep nesting with
/usr/compilers/suncc2008.11? All other cases use (say)
/usr/suncc/2008.11, as I've mentioned several times before.
* Where's the need for this level of granularity. If the plan is to
integrate successive releases of Studio Express, I cannot see a reason to
have them installed in parallel (I see them as similar to Studio 12 +
Patches, which aren't installed in parallel either). On the other hand,
this creates a usability problem: if the intention is to install
different versions of the Studio compilers in parallel (which certainly
makes sense e.g. for Studio 12 + Studio Express), the user is not
generally interested in which particular delivery (or patch level) of the
Studio tools he is using, only in the distinction between Studio 12 and
Express. If he wants to specificially select Studio Express when Studio
12 is installed as well, in the proposed scheme he has to update his PATH
every time a new delivery is included (which could be as often as every
three months), instead of selecting Studio Express vs. Studio 12 once.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
