On Fri, 13 Feb 2009, Manuel Prinz wrote:
This would be really nice! As for Git, there are two things to concider: First, we probably need to agree to the name of the branch in which the debian/ files exist: some use "master", some "debian", or whatever seems to fit. Second, one has to consider that Git repos may be bare, so you can not access the files directly. This is not really a problem, one can access them without the need to clone the repo. (I have a shell script to do so for use with mr.) I guess this can be done in Python as well.
Sounds good.
Both of them are no show stopers, I just wanted to write it down so it's not forgotten. Hopefully I'll find the time to help implementing that soon.
I think we have some time. I just became excited about UDD and I will probably work on rewriting the methods I get package info to use UDD instead of Packages.gz first which is much more clever and more reliable. While thinking about UDD it might be reasonable to find a way to inject the info we need for prospective packages to UDD or DDE. This might be interesting also for non-Blends issues and finding a general solution seems to be more clever. Later we might be easily able to select the data we need for a Blend in question. Kind regards Andreas. -- http://fam-tille.de