Though this case is about bundling the Sun C and C++ compilers with Nevada, the case does note how the versions of the unbundled Sun Studio compilers coexist with the bundled compilers and each other. The case also notes how the unbundled Sun Studio compilers can override the links established by the bundled compiler in /usr/bin and links established by other versions of Sun Studio.
Douglas John Plocher wrote: > On Thu, Jan 15, 2009 at 9:34 AM, Chris Quenelle <Chris.Quenelle at sun.com> > wrote: >> In the latest proposal, the bundled compiler binaries are not versioned, >> and neither are the man pages. If you want multiple versions of the >> compilers, you can install as many different versions of the >> unbundled product as you want. This case is about choosing one >> version to bundle into the OS as the default compiler. > > > This case *should* be about setting up a structure that allows for > both the bundled and unbundled compilers to coexist and evolve in a > coordinated way. The customer doesn't care one bit about whether Sun > considers a particular version to be bundled or not; history shows > that Sun changes its mind often about this sort of thing. The > architecture shouldn't be tied to such marketing distinctions either. > > A scheme like the current studio compilers one would work well: > > /usr/suncc/$version/[bin, lib, man, ...] > > A separate <something> should be used to manage the concept of > "default". Links to /usr/bin, management of a /usr/suncc/latest > symlink, whatever should all be architecturally independent from the > delivery of a versioned compiler instance. > > -John
