jakarta-commons-*.spec naming

[Paweł Zuzelski]

On Friday 10 of October 2008 01:11:05 wrobell wrote:
> On Fri, Oct 03, 2008 at 11:06:32PM +0300, Elan Ruusamäe wrote:
> > On Friday 03 October 2008 22:24:19 Jacek Konieczny wrote:
> > > On Fri, Oct 03, 2008 at 10:04:52PM +0300, Elan Ruusamäe wrote:
> > > > i understand that we need to rename packages that have moved to
> > > > http://commons.apache.org
> > > >
> > > > how do we call them?
> > > >
> > > > - apache-commons-io (*)
> > > > - commons-io
> > > > - java-commons-io
> > > > - java-apache-commons-io
> > > >
> > > > (*) i prefer this one, unless it rises some additional confusion or
> > > > restruction due name use...
> > >
> > > I prefer the third ("java-commons-io") and I would be happy to see
> > > similar change for all java libraries. This way they would be grouped
> > > like python or perl modules. And there would be no confusion because
> > > of the http server in 'apache' package or because library names looking
> > > like application names.
> >
> > sounds sane,
> > but this ("java-" prefix) would apply only to libraries not applications?
> >
> > i mean tomcat, jAlbum won't be named as java-apache-tomcat, java-jAlbum,
> > java-gallery-remote.. ?
>
> only libs like in case of python, i.e. python-psycopg2 (lib) but gaphor (an
> app).

What about packages like beanshell? It may be used as java libraries and as 
stand-alone application. Should we rename it to java-...?

-- 
    .....        Pozdrawiam,                                             .....
  .....              Pawel Zuzelski                                    .....
.....     jid:pzz at touk.pl                                            .....