[csw-maintainers] need of an additional directory tree under /opt/csw

[Dagobert Michelsen]

Hi Dominique,

first, your GCCfss 4.3.2 and 4.3.3 have been installed on current9s  
and current10s.

Am 18.08.2010 um 00:22 schrieb Dom:
> these are tough questions for me. As Peter mentioned, having well- 
> identified packages would make life easier for other maintainers who  
> have similar dependencies. To the question "why" I need gcc/g++  
> compiled libraries, I just can answer the following: more that 440 c+ 
> + source files to hack in order to be "Sun-Studio compliant" is a  
> lot of too much work for me, just to have binaries available on Sun  
> Solaris (yes: Sun Solaris, and not Oracle Solaris :-)). I had some  
> cheat chat with the main developers of Kicad and they just answered  
> to me: "we only support Gcc". And indeed: all the patches I  
> submitted to them in order to have C++ code without any GCC specific  
> extensions were refused !
> I have no problem embedding specific dependencies within each  
> packages, even if some of them have to be installed twice or more.  
> It is just a question of "quality" for me...
> BTW: the incoming Kicad package I'll release will NOT include the  
> "dev" version of WxWidget 2.8.11 I had to provide internally. So  
> will it be for Erlang. Funny is that Kicad depends on Erlang, and  
> both depend on WxWidgets. And I'll have the same case with "boost",  
> unfortunatly.
>
> But this still remains subject to change... for the next versions !

I think it would be cleanest to have a convention for gcc-compiled c++  
libs,
like
   CSW<pkg>lib is the Sun Studio version
   CSW<pkg>lib-gcc is the gcc compiled version
Then there should also be a standard place for these libs. I propose
   /opt/csw/lib/gcc/mylib.so
   /opt/csw/lib/gcc/amd64/mylib.so
   /opt/csw/lib/gcc/64 -> (amd64|sparcv9)
These links should be delivered by CSWlibgcccommon.

Thoughts?


Best regards

   -- Dago