On Mon, Nov 12, 2012 at 1:27 AM, Steffen Schwigon wrote: > > > Let's take as a sample case Test::Class. It have a meaningless test > > fail, a patch waiting in the RT, and a lot of modules depending on it. > > How can I find the list of modules that directly depend on it? > > metacpan's reverse-dep give indirect deps too. I will file a bug to > > all of them, and let's see what will happen. > > That's a great example, really. Because you already *have* the issue and > patch available. > > Why would you inform all the dependent modules if the root cause is > already known? From a single RT ticket which needs to be pushed you want > to multiply that onto all affected modules? >
because I'm trying to simulate an automated process, as Andreas Koenig suggested. There are people that are trying to fix CPAN manually, most notably (at least recently) is Shlomi Fish. You can see his emails asking for comaint popping up in the authors list. I'm lazier then him, and seek systematic solution to systematic problem. By that rationale a bug in a Perl core module would require a ticket in > all 20_000 CPAN distros. > Fortunately, the Perl core is quite stable and well tested. But the problem is not if there is some bug in the underlying software. Bugs are OK. we can work around them. If my tests fails because of a bug in some module, I will know about it, and can workaround it, or contact the author of that module so he will fix it. or use other module. I can do something about it. But if it fails to install, I don't know about it. so I can't do anything about it. Shmuel.
