>> 4.5. Interfaces: >> >> Exported Interface >> >> Interface Classification Comments >> ----------------------------- -------------- ---------------------- >> SUNWraptor Uncommitted Package name >> SUNWraptor-devel Uncommitted Package name >> /usr/bin/rapper Volatile parser utility >> /usr/bin/raptor-config Volatile config utility >> /usr/lib/libraptor.so.1 Volatile library >> /usr/share/man/man1/rapper.1 Volatile man page >> /usr/share/man/man1/raptor-config.1 >> Volatile man page >> /usr/share/man/man3/libraptor.3 Volatile man page >> /usr/lib/pkgconfig/raptor.pc Volatile pc file >> /usr/include/raptor.h Volatile Header file >> /usr/share/gtk-doc/html/raptor Volatile help file
Some comments: 1. Man pages aren't interfaces and shouldn't be included here. 2. Documentation isn't an interface and shouldn't be include here. 3. Individual include files don't need to be specified. 4. Package classifications should match interface classifications. 5. Library symlink should be provided. Here's what I end up with: Interface Classification Comments ----------------------------- -------------- ------------------ SUNWraptor Volatile Package name SUNWraptor-devel Volatile Package name /usr/bin/rapper Volatile parser utility /usr/bin/raptor-config Volatile config utility /usr/lib/libraptor.so Volatile library symlink /usr/lib/libraptor.so.1 Volatile library /usr/lib/pkgconfig/raptor.pc Volatile pc file /usr/include/ Volatile Header files Also, it would be good for the desktop community to evaluate the current strategy of only delivering 64bit libraries as needed. It's normally easier for engineers to produce both archs at the time of initial putback then later, and we are seeing more and more interest in community members wanting to produce 64bit ready desktops. Because of this, "as needed" strategy it creates a barrier. If you are concerned about space, you could include the 64bit libraries only in the devel packages for now. Cheers, Jim
