Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

Guillem Jover guillem at debian.org
Fri Aug 9 03:53:36 BST 2019


On Wed, 2019-08-07 at 16:19:30 +0200, Axel Beckert wrote:
> Guillem Jover wrote:
> > Some of the features got removed, to trim down dependencies, and the
> > API adapted to match the rest of the libdpkg-perl codebase, but if
> > the removed output formats are needed, or anything else seems
> > suboptimal or worth improving/adding, I'm happy to work on those.
> 
> What I quickly checked a few weeks ago was if libdpkg-perl has an
> equivalent of parsechangelog which is used in aptitude. But it hasn't,
> so I didn't consider it to be a suitable replacement.
> 
> And your patch against aptitude (see https://bugs.debian.org/934135)
> uses "perl -MDpkg::Changelog::Parse -e …" which probably works well,
> but having a drop-in replacement for /usr/bin/parsechangelog which is
> not in dpkg-dev would be nice.

I'm not very fond of placing programs in lib.*-perl packages TBH. I've
pondered in the past to split some of the tools out from dpkg-dev, but
I'm not really sure it is worth it. And checking again, for the
aptitude case I think a local aptitude-specific wrapper makes more
sense. I'm sending a follow-up patch there.

Thanks,
Guillem



More information about the pkg-perl-maintainers mailing list