Proposal for a standard for D library naming

[Gregor Richards]

Since there seems to be a lot of confusion as per the purpose of this 
library naming convention, I've added the following section:

Purpose

As there is much misunderstanding of the purpose of this library naming 
convention, it's outlined here:

     * The Library Naming Convention has no bearing whatsoever over the 
names or arrangement of source files.
     * The Library Naming Convention does not intend to replace 
build-style 'build everything from source with include paths' building, 
it intends to be a superior alternative.
     * The Library Naming Convention is a convention. That is, no one is 
required to conform to it, but (were it to be accepted) it would be 
inconveniencing not to.
     * The Library Naming Convention allows the source maintainer to 
choose what packages to make into libraries, with what level of 
division, etc. It has few rules over what is and what isn't in given 
libraries, as its purpose is the naming of libraries, not the content.
           o The only rule is that any module must be in the most 
specifically-named library corresponding to that module. That is, if you 
have libD.a.b.so.0 and libD.a.so.0, the module a.b.c should be in 
libD.a.b.so.0, not libD.a.so.0. Doing otherwise is fairly ridiculous anyway.



http://www.prowiki.org/wiki4d/wiki.cgi?LibraryNamingConvention