Re: Bug#420165: ITP: commons-configuration -- Java based library providing a generic configuration interface
On 4/21/07, Damián Viano <firstname.lastname@example.org> wrote:
Mmm... I think commons-configuration can be a slightly misleading
name, how about libcommons-configuration-java following lots of
libcommons-* packages already in the archive?
A full name would be: libapache-jakarta-commons-configuration-java
which is a bit too long.
Asking google for 'commons configuration' points you to the homepage
of the package. I call the binary package
libcommons-configuration-java but not the source package. Do we have
any written policy about source package names for libraries? At least
I am not aware of such a policy for other languages like C/C++: it's
called glibc not libc-c or alsa-lib not libasound2-c or lesstif2 not