Skip Menu |

This queue is for tickets about the CPANDB CPAN distribution.

Report information
The Basics
Id: 49352
Status: open
Priority: 0/
Queue: CPANDB
People
Owner: Nobody in particular
Requestors: cpan [...] prather.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.10
Fixed in: (no value)

History Show all quoted text
  Tue Sep 01 23:10:02 2009 cpan [...] prather.org - Ticket created
Subject: No (easily discovered) way to generate a simple list of upstream dependencies
I was trying to generate a list of dependences and found that the only solution was to install a graphing module and generate a graph. CPANDB::Distribution has all the logic I would need to generate a simple list but the logic is too tightly coupled with adding to a graph that I couldn't easily extract it in the *mumble* minutes I looked at it while writing up a blog post. If I get a chance I'll circle back around with a patch for callbacks or something.
  Wed Sep 02 03:46:32 2009 adam [...] ali.as - Correspondence added
Subject: Re: [rt.cpan.org #49352] No (easily discovered) way to generate a simple list of upstream dependencies
Date: Wed, 2 Sep 2009 17:46:09 +1000
To: bug-CPANDB [...] rt.cpan.org
From: Adam Kennedy <adamkennedybackup [...] gmail.com>
Just to confirm, you want a raw order-irrelevant bulk list of all recursive dependencies (and/or dependants, might as well do both) that contains no information about why anything is in the list, but just gives the names? Adam K 2009/9/2 Chris Prather via RT <bug-CPANDB@rt.cpan.org>: Show quoted text
> Tue Sep 01 23:10:02 2009: Request 49352 was acted upon. > Transaction: Ticket created by PERIGRIN >       Queue: CPANDB >     Subject: No (easily discovered) way to generate a simple list of upstream >  dependencies >   Broken in: 0.10 >    Severity: Normal >       Owner: Nobody >  Requestors: cpan@prather.org >      Status: new >  Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=49352 > > > > I was trying to generate a list of dependences and found that the only > solution was to install a graphing module and generate a graph. > CPANDB::Distribution has all the logic I would need to generate a simple > list but the logic is too tightly coupled with adding to a graph that I > couldn't easily extract it in the *mumble* minutes I looked at it while > writing up a blog post. > > If I get a chance I'll circle back around with a patch for callbacks or > something. >
  Wed Sep 02 03:46:33 2009 The RT System itself - Status changed from 'new' to 'open'
  Wed Sep 02 17:24:33 2009 chris [...] prather.org - Correspondence added
CC: cpan [...] prather.org
Subject: Re: [rt.cpan.org #49352] No (easily discovered) way to generate a simple list of upstream dependencies
Date: Wed, 2 Sep 2009 17:24:07 -0400
To: bug-CPANDB [...] rt.cpan.org
From: Chris Prather <perigrin [...] gmail.com>
On Wed, Sep 2, 2009 at 3:46 AM, Reserved Local Account via RT<bug-CPANDB@rt.cpan.org> wrote: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=49352 > > > Just to confirm, you want a raw order-irrelevant bulk list of all > recursive dependencies (and/or dependants, might as well do both) that > contains no information about why anything is in the list, but just > gives the names? > > Adam K
Well I assumed from a quick glance at the code that a callback system would naturally order by the same breadth first search that the current system uses. But effectively "yes" ... I just want something to spit out a list of "if you install $A you will also get @B". The point of this original request was so that I could build an accurate list of the modules for Moose without having to render them as a graph. And yes dependents would be useful too "if you break $Y ... you will also break @Z" would be useful in generating a list of say downstream notification emails saying "I'm about to break back-compat please test the current Developer Release" or something similar. -Chris