Re: Upstream maintainer disagree with the package name
Rémi Perrot wrote:
> I recently upload a new package called libglade-perl. After some mail
> exchange with the upstream maintainer (Dermot Musgrove
> <dermot@glade.perl.connectfree.co.uk>), he say that libglade-perl is not
> a library and he ask me to change the name of the package to glade-perl.
>
> He is not wrong since in fact it is a perl generator that use perl class
> embedded in perl module. The package also provide a perl executable that
> may violate some policy.
> -rw-r--r-- root/root 74828 2001-02-10 17:07:33 ./usr/lib/perl5/Glade/PerlUIGtk.pm
> -rw-r--r-- root/root 27439 2001-02-10 17:07:33 ./usr/lib/perl5/Glade/PerlProject.pm
> -rw-r--r-- root/root 73210 2001-02-10 17:07:33 ./usr/lib/perl5/Glade/PerlUI.pm
> -rw-r--r-- root/root 50473 2001-02-10 17:07:33 ./usr/lib/perl5/Glade/PerlSource.pm
> -rw-r--r-- root/root 47475 2001-02-10 17:07:33 ./usr/lib/perl5/Glade/PerlGenerate.pm
> -rw-r--r-- root/root 22626 2001-02-10 17:07:34 ./usr/lib/perl5/Glade/PerlRun.pm
> -rw-r--r-- root/root 11532 2001-02-10 17:07:33 ./usr/lib/perl5/Glade/PerlXML.pm
> -rw-r--r-- root/root 43005 2001-02-10 17:07:33 ./usr/lib/perl5/Glade/PerlUIExtra.pm
> -rwxr-xr-x root/root 1520 2001-05-19 10:01:33 ./usr/bin/glade2perl
Since it includes an executable that presumably uses the files in
/usr/lib(should be /usr/share), it can go either way.
Do the perl modules even have a well defined and exported interface, or
are they internal modules for use by the program?
If they are for internal use, well, there are some high profile examples
of programs including internal use perl modules in them and not being
named lib*-perl. For example, alien, debconf, and debhelper all do this.
Even if the modules have a well defined interface that might be used by
other stuff, it's something of a judgement call whether the lib*-perl
name is mandated. We use the lib*-perl names so users can install perl
modules easily, without having to look up the package name, if they know
the module name; and so packages can easily declare dependancies on the
modules they use. If this kind of thing is likely for this package, you
might want to name it libglade-perl. Or you could compromise and name it
glade-perl or whatever, and make it provide libglade-perl. Or the other
way round..
--
see shy jo
Reply to: