Re: Bug#532932: ITP: libalien-libjio-perl -- Perl package to find libjio
Hm, fair enough. I'll close the bug; and will not package the Alien module.
This also makes me wonder though, should a similar fate befall
libalien-wxwidgets-perl?
aven'jon(~/alien-jio/Alien-Libjio/t)> apt-cache rdepends libalien-wxwidgets-perl
libalien-wxwidgets-perl
Reverse Depends:
libwx-perl
So if libwx-perl is patched, then libalien-wxwidgets-perl could be
made obsolete... On the other hand, even if this isn't something we'd
like in the future, maybe we could set a policy for that. I'll e-mail
debian-policy in a few days (pending any further discussion on these
lists first - debian-devel and debian-perl) to get some clarification
on this.
Thanks :-)
Jonathan
On Fri, Jun 12, 2009 at 7:50 PM, Ryan Niebur<ryanryan52@gmail.com> wrote:
> On Fri, Jun 12, 2009 at 07:29:40PM -0400, Jonathan Yu wrote:
>> Brian:
>>
>> On Fri, Jun 12, 2009 at 5:57 PM, brian m.
>> carlson<sandals@crustytoothpaste.ath.cx> wrote:
>> > On Fri, Jun 12, 2009 at 05:14:29PM -0400, Jonathan Yu wrote:
>> >> This module is a generic Perl module that is designed to install libjio if it
>> >> is not installed, and then report the flags required for programs to link to
>> >> it. Under Debian, installing libjio via this package is not necessary (since
>> >> it can simply Build-Depend and Depend on the libjio package itself.
>> >>
>> >> However, the Perl module still needs to be installed so that Perl programs can
>> >> find it, and the flags required to link to it. This will be useful if modules
>> >> other than simply IO::Journal (later to be ITP'd as libio-journal-perl, once
>> >> it is appropriately uploaded to CPAN).
>> >>
>> >> Luckily, since only the Perl stuff is going to be installed, then it's not
>> >> likely we'll ever need to really upgrade this module...
>> >
>> > Can't you just patch the modules in question so that they don't need to
>> > use this module? It seems silly to create a module just to make sure
>> > that a dependency is installed. That's for the Perl module building
>> > system or dpkg to ensure.
>> That is a very good point. However, I'm just not sure if other modules
>> will want to use Alien::Libjio -- it has a few methods that wrap
>> around pkg-config and ExtUtils::Liblist, so that you can get compile
>> flags and linker flags (that applications need to compile XS bindings
>> against libjio).
>>
>
> you meantion that other modules may want to use it...well, then lets
> deal with packaging that when this happens. there's no reason to right
> now.
>
> --
> _________________________
> Ryan Niebur
> ryanryan52@gmail.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkoy6dEACgkQMihv+PacasUXMwCfTC5i9PcNiJGxq26AGY6Jr5xF
> HDYAoNKQmdPoV9OkT62GzqM1n1koj3bg
> =+CrV
> -----END PGP SIGNATURE-----
>
>
Reply to: