Darren Kenny wrote:
> The main benefit of having libraries in a public location is that people will
> use them - while these libraries are dependencies of some apps, they are also
> very useful for more rapid desktop development - making something 
> Consolidation
> Private really defeats this purpose.

+1


> I think we need to get away from the idea of Consolidations a bit, since
> OpenSolaris really breaks down these barriers and I think it would be pity to
> raise them again out there.

+0 - IMO, we need to drastically shrink the sizes of our consolidations - and
raise the number of them.  For example, each and every FOSS thing should be
its own consolidation - it delivers as a unit, it has its own versioning, etc.
IPS and repositories are tools that let us do that.


> 
> We really need to get C++ sorted for Solaris/OpenSolaris - we all use a CBE 
> for
> Solaris - and OpenSolaris AFAIK - could we not just ensure that at least this
> works for people out of the box, clearly stating the C++ compiler to use.

That's why the rule is "if you do this, you must use studio".


> Is there some way that the compiler and linker could work together to flag a
> possible issue at run-time of the app and libs version of C++ compiler don't 
> match?


They do - the error is usually "Symbol not found" :-)


> It would actually be easier if the C++ compiler was simply there by default
> after installation so that there is less risk of someone installing the "wrong
> one"...

+1000

   -John

Reply via email to