IPv6 enabling more modules (or: how to find reverse dependencies)
- To: firstname.lastname@example.org
- Subject: IPv6 enabling more modules (or: how to find reverse dependencies)
- From: Per Carlson <email@example.com>
- Date: Thu, 7 Jun 2012 22:34:51 +0200
- Message-id: <CAOURYnAz+ptbp4sq3dk6zqy4ktqChFOg3NpwQDZRprnJU=5LBQ@mail.gmail.com>
I have spent some time trying to IPv6 enable one of my frequently used
modules, libnet-telnet-perl, without much luck. All efforts to replace
IO::Socket with IO::Socket::IP (or Socket) have so far been fruitless.
I was aiming doing just minor changes, and thus creating a limited
diff, but it looks like a major rewrite is needed.
Instead of beating my forehead bloody on that module, I'm thinking on
a new plan: work on modules depending on IO::Socket::INET.
But there I hit a really hard obstacle: which modules do depend on
IO::Socket::INET? As this module is part of perl-base, there is no
easy way to find the reverse dependencies using dpkg/apt/etc. Is there
an easy/not too hard way to find those? The only viable method I can
think of is greping through the source code of all modules.
"D’ä e å, vett ja”, skrek ja, för ja ble rasen,
”å i åa ä e ö, hörer han lite, d’ä e å, å i åa ä e ö"
- Gustav Fröding, 1895