On Mon, Jun 07, 2010 at 04:20:22PM +0200, Holger Levsen wrote: > mind if we keep debian-devel in the loop? If not, please reply to > debian-devel@lists.debian.org and quote me freely :-)
of course not! > [...] > Do you plan to package this for Debian? Then I could easily re-use it on > piuparts.debian.org :) If not, a textfile with that list updated daily for > stable, testing and sid would also help (me now), but be less robust and > useful for others. it does produce a text file for unstable which you can get at http://debian.semistable.com/unstable_raw.txt if you need the same for testing and stable just give me a shout. packaging this really doesn't make much sense as long as teh code is in the bad state it currently is in. which isn't really a coding problem, but more that i would need input from other people. quoted from my earlier mail to holger for background: > the code that produces that page is a branched and hacked version of the > one here: https://debian.semistable.com/svn/debgraph/ > > unfortunately this is in a weird state. the original idea was to produce > a big graph of all sorts of relations between source packages, binary > packages, distributions, version, architectures, maintainers, bugs etc > and then have a functional language in which to formulate queries > against it. the goal was to create something like lintian, but for the > relationships between entities. i still think it is a splendid idea, but > it kinda got stuck, mostly for the lack of someone to discuss > applications of it with. the circular dependency check is just an > example of what you can do with it, and not a very good one. so if anyone can think of good use cases for a tool that allows analytics on the dependencies between entities in the debian space (packages, bugs etc), then please send them my way. with a moderatly long list of use cases, i could go on defining the query language... cu rober -- Robert Lemmen http://www.semistable.com
signature.asc
Description: Digital signature
