Graig, I like your idea. Let me dig it a bit. Assuming that all sources are under some URL, some quick release checks can be delegated to search engines [1], [2]. Having the whole list of release checks, we may form a requirement list to the next generation of the search engine, thus defining a way public search engine specs would evolve. I imagine a day when a static code analyzer would contact you by email describing a bug in your newly committed code.
[1] http://www.google.com/codesearch?q="strictly+prohibited"; [2] http://kottke.org/06/10/google-code-search On Wed, Apr 15, 2009 at 3:51 AM, Craig L Russell <[email protected]> wrote: > Usually, proposed releases are posted to a url like this one: > > http://people.apache.org/~shanti/olio_0.1/ > > There, the actual artifacts, signatures, and md5 sums are located. > > Does rat have the ability to list the contents of a url directory, download > and check the artifacts' signatures and md5 sums, then unzip/untar the > artifacts and do its usual license checking on the results? > > If not, I'd like to take a crack of writing this implementation. In Java, it > should only take a few hundred lines of code. Perhaps 20 lines in Ruby? > > Craig > > Craig L Russell > Architect, Sun Java Enterprise System http://db.apache.org/jdo > 408 276-5638 mailto:[email protected] > P.S. A good JDO? O, Gasp! > > -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://www.telecom-express.ru/ http://people.apache.org/~aaf/ http://harmony.apache.org/ http://code.google.com/p/openmeetings/
