#446872 libjcode-pm-perl: Debian package should be named 'libjcode-perl'

Package:
libjcode-pm-perl
Source:
libjcode-pm-perl
Description:
Perl extension interface to convert Japanese text
Submitter:
Ilya Martynov
Date:
2025-06-11 16:11:02 UTC
Severity:
wishlist
#446872#5
Date:
2007-10-16 10:35:09 UTC
From:
To:
The Debian package for this Perl module should be named
'libjcode-perl' instead of 'libjcode-pm-perl' to be consistent with
naming scheme for all other Debian packages for Perl modules.

#446872#10
Date:
2025-06-11 06:40:40 UTC
From:
To:
Hi,

thank you for this bug report - even if it remains not answered
for an extremely long time.

Am Tue, Oct 16, 2007 at 02:35:09PM +0400 schrieb Ilya Martynov:

I wonder if this is a good idea.  There is another package named
libjcode-perl[1] which is maintained by the same author and which
is definitely different from this package.

I intend to migrate libjcode-pm-perl to the Debian Perl team.  It
also has at least one new upstream version and definitely deserves
some more love.  However, I would like to get some input from
Perl team about the naming scheme.

Kind regards
    Andreas.

[1] https://tracker.debian.org/pkg/libjcode-perl

#446872#15
Date:
2025-06-11 09:30:44 UTC
From:
To:
Quoting Andreas Tille (2025-06-11 08:40:40)

lib*-perl packages are generally expected to match CPAN projects.

It seems neither of the projects mentioned here are on CPAN, so I wonder
if perhaps more sensible for *both* of them to (encurage upstream to
begin using CPAN, and otherwise) avoid the lib*-perl namespace in Debian
for either of them - and at least stop introduce any new packages using
that confusing conflation of namspace for anything-written-in-perl.

 - Jonas

#446872#20
Date:
2025-06-11 09:35:14 UTC
From:
To:
[sent again via X-Debbugs-Cc to please Microsoft-based iponweb.net]

Quoting Andreas Tille (2025-06-11 08:40:40)

lib*-perl packages are generally expected to match CPAN projects.

It seems neither of the projects mentioned here are on CPAN, so I wonder
if perhaps more sensible for *both* of them to (encurage upstream to
begin using CPAN, and otherwise) avoid the lib*-perl namespace in Debian
for either of them - and at least stop introduce any new packages using
that confusing conflation of namspace for anything-written-in-perl.

 - Jonas

#446872#25
Date:
2025-06-11 10:40:58 UTC
From:
To:
perl 5.

I guess that -pm- was added to distinguish between the perl 4 and perl 5
libraries.

We may want to drop libjcode-perl as it has not reverse dependencies and perl
4 has not been shipped by Debian for quite a while.

Then, we may rename libjcode-pm-perl to the old name. I not clear on the
process involved to avoid confusion with the old libjcode-perl package.

The question is: is this rename worth the trouble ?

HTH

#446872#30
Date:
2025-06-11 12:36:09 UTC
From:
To:
Hi Jonas and Dominique,

thank you both for your comments

Am Wed, Jun 11, 2025 at 12:40:58PM +0200 schrieb Dominique Dumont:
ITS bug #1107307 into a pre-removal warning and if not answered turn
this into a removal request.

Most probably not - at least not for the moment.  I intend to move
libjcode-pm-perl to Debian Perl group maintenance.  The former
maintainer seems to be inactive for several years.  The decision whether
to rename or not might be drawn later once libjcode-perl was removed.

I agree with Jonas that the package will profit from being maintained
at CPAN and will suggest this to the author.

Kind regards
    Andreas.

#446872#35
Date:
2025-06-11 14:27:03 UTC
From:
To:
started a draft earlier.]

I would say: It's a mess :)

libjcode-pm-perl
- is the package for the CPAN distribution Jcode [0]
- and installs /usr/share/perl5/Jcode.pm [1]
- so typically we would name it, as the bug submitter suggests,
   libjcode-perl

Which doesn't work in this case, as there is this libjcode-perl
- which installs /usr/share/perl5/jcode.pl [2] and
- comes from ftp://ftp.iij.ad.jp/pub/IIJ/dist/utashiro/perl/ [3],
   also reachable as http://ftp.iij.ad.jp/pub/IIJ/dist/utashiro/perl/

Looking at https://ftp.iij.ad.jp/pub/IIJ/dist/utashiro/perl/jcode.pl-2.13-manual.txt
I wonder if packaging this makes a lot of sense …

% popcon -v libjcode-perl ; reverse-depends libjcode-perl ; reverse-depends -b libjcode-perl
       PACKAGE SUM        VOTE       OLD        RECENT     NO FILES
libjcode-perl 89         1          1          0          87
No reverse dependencies found
No reverse dependencies found

So yay, libjcode-perl looks like a removal candidate.


% popcon -v libjcode-pm-perl ; reverse-depends libjcode-pm-perl ; reverse-depends -b libjcode-pm-perl
          PACKAGE SUM        VOTE       OLD        RECENT     NO FILES
libjcode-pm-perl 14346      325        13474      545        2
Reverse-Depends
===============
* chalow
* libspreadsheet-parseexcel-perl
* libunicode-maputf8-perl

Packages without architectures listed are reverse-dependencies in: all, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64, s390x
Reverse-Build-Depends-Indep
===========================
* libspreadsheet-parseexcel-perl
* libunicode-maputf8-perl


This looks more sensible, even if the package name is a bit
unfortunate; but I guess doing the rename dance is more effort than
it's worth.


Cheers,
gregor


[0] https://metacpan.org/dist/Jcode
[1] https://packages.debian.org/sid/amd64/libjcode-pm-perl/filelist
[2] https://packages.debian.org/sid/all/libjcode-perl/filelist
[3] https://tracker.debian.org/media/packages/libj/libjcode-perl/copyright-2.13-4.1

#446872#40
Date:
2025-06-11 16:09:36 UTC
From:
To:
Hi Gregor,

Am Wed, Jun 11, 2025 at 04:27:03PM +0200 schrieb gregor herrmann:

OK, so I'll turn my previous ITS into a pre-removal.

I'll file an ITS on behalf of Debian Perl team for this one
and will tag the bug asking for removal `wontfix`.

Kind regards
    Andreas.