Bug#642819: libencode-imaputf7-perl: Unknown encoding 'IMAP-UTF-7'

Damyan Ivanov dmn at debian.org
Sun Sep 25 19:37:49 UTC 2011


-=| Niko Tyni, 25.09.2011 16:47:11 +0300 |=-
> On Sun, Sep 25, 2011 at 03:00:18PM +0300, Damyan Ivanov wrote:
> > severity 642819 minor
> > retitle 642819 libencode-imaputf7-perl: synopsis misses 'use Encode::IMAPUTF7;'
> > thanks
> > 
> > -=| alexander barakin (aka sash-kan), 25.09.2011 13:31:44 +0300 |=-
> > > Package: libencode-imaputf7-perl
> > > Version: 1.05-1
> > > Severity: important
> > > 
> > > $ perl -e "use Encode qw/encode decode/; print decode('IMAP-UTF-7',
> > > 'R&AOk-pertoire');"
> > > Unknown encoding 'IMAP-UTF-7' at -e line 1
> > 
> > This is a documentation problem. Try adding 'use Encode::IMAPUTF7;'
> 
> Alternatively, as hinted by the INSTALL file, one can use 'enc2xs -C'
> to include the module in /usr/lib/perl/5.12/Encode/ConfigLocal.pm,
> making just 'use Encode' work.

Hmm. I missed that.

> Not sure if that should be done by the libencode-imaputf7-perl 
> postinst script. At the very least, /usr/lib/ looks to me like 
> a wrong place for the generated file in that case  - but that's in 
> the domain of the 'perl' package, which provides enc2xs.

We could do that, in both postinst and postrm. Could it be done by 
a dpkg trigger? That would be really neat :)

ACK on the unsuitability of /usr/lib. I guess that could be solved by 
a symlink to /var/lib?

> Possibly this needs some more plumbing in the 'perl' package first.
> However, this is the first request I'm aware of for automatically updating
> the list of encodings supported by Encode at package installation time,
> so it looks like the demand isn't too high.

Right. I for one wasn't even aware of the existence of enc2xs and its 
mechanism :)

I guess no CPAN distribution invokes that during its installation. 
Grepping over pkg-perl's 2100 packages shows only one mention, in 
libencode-imaputf7-perl's INSTALL file, and two packages use it during 
build -- libencode-hanextra-perl and libencode-jis2k-perl.

That said, if there is a trigger that makes encodings instantly 
available without "using" them, to me it seems like a nice thing to 
have, regardless of how many packages currently "push" in that 
direction.

Would that be too much of divergence from upstream?


 -- dam
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20110925/da8e94c6/attachment.pgp>


More information about the pkg-perl-maintainers mailing list