Simon: > Glibmm is a set of C++ bindings for Glib2 Library, including > cross-platform APIs such as a std::string-like UTF8 string class, string > utility methods, such as a text encoding converter API, file access, and > threads. > > Spec files are based on SFE version and changed a little. Please > review.
It isn't clear to me why these interfaces are needed in Nevada. What uses these C++ bindings? Is there anything that we intend on shipping in GNOME 2.22 (or later) that depends on these? If nothing really depends on them, I think it would make more sense to not ship them. People who need them can build them from SFE, no? As has been mentioned by others, ABI incompatibilities between GCC and Sun Studio complicate things. ABI is not even guaranteed to be compatible between different versions of the same compiler. Others have recommended that we consider shipping versions of the library interfaces built with both Sun Studio and GCC compilers. When we last talked with ARC about this, there is the following additional requirement when shipping C++ interfaces. - You must have a section 3 manpage which explains what compiler and what version of the compiler was used to build each version of the library provided. So, it is the module owners responsibility to ensure that the manpage is provided and properly updated anytime the version # of the compiler changes that we use to build the interfaces with. Brian
