On Thu, Feb 07, 2008 at 04:24:55PM -0800, John Fischer wrote: > 4.2. Interfaces: > > -------------------------------------------------------------------- > Exported Stability Comments > > -------------------------------------------------------------------- > SUNWlibcddb Uncommitted Package > name > libcddb.so Volatile C library > CDDB protocol Volatile
Erm, same comment on Volatile here as everywhere else. It's quite clear we need some mechanism that allows us to feel free to change these components, possibly breaking all consumers, on a frequent basis, but without the contract hell that Volatile requires. Regardless of that discussion, I'd say that if the CDDB protocol isn't Committed, then it should be Private, or maybe Committed Private. And we need to be careful about giving the ".so" name of the library, rather than the actual SONAME, too. > /usr/demo/libcddb/ Not an Interface *NEW* > Folder > cddb_query Not an Interface demo CLI > utility Why not just put this in /usr/bin? > SUNWlibcddb-devel Uncommitted Package > name > /usr/include/include/cddb Uncommitted /usr/include/include? > Header files under include/cddb Volatile What's the point in having the directory uncommitted but all the header files volatile? > libcddb.pc Volatile Meta > information > for > pkg-config This really has no business being anything less than Uncommitted. > -------------------------------------------------------------------- > Imported Stability Comments > > -------------------------------------------------------------------- > HTTP Protocol Committed Standard HTTP > protocol > CDDB Protocol Volatile From FreeDB.org As a project, this doesn't import CDDB, it exports it, or at least it would if it were giving it a higher stability level. Danek
