From: Holden Glova <dsafari@...>
Date: 2001-12-24T09:02:14+09:00
Subject: [ruby-talk:29384] Re: raa.succ top 5!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 24 Dec 2001 11:21, patrik wrote:
> On Mon, Dec 24, 2001 at 12:37:30AM +0900, Niko Schwarz wrote:
> > Jim Menard wrote:
> > > 1) Keyword searches. Maintain lists of pre-defined keywords
> > > that project authors can use to describe their projects. Let
> > > project authors add or submit new keywords. Then raa.succ can
> > > respond to queries like "list all database projects" or "list
> > > all gui builder projects".
> > >
> > > 2) Dependencies. Let a project author define which other
> > > projects (and version numbers) are required for their project.
> > >
> > > 3) When retrieving a project, automagically grab all other
> > > projects that the project depends on.
> >
> > 4) A list of platforms under which you can run it for each
> > project
>
> 5) Be based on the RubyGems project and for crossplatform building
> maybe also the talked about ruby make replacement.
>
> on a sidenot: I think both RubyGems, "standalone ruby
> executables"-project and rdoc could cooperade on a good dependency
> graph generator class(es)), they would all need that functionality
> and we don't want to violate the DRY principle :)
>
> /Patrik

Hmm..I'm not sure how this sort of thing works (dependency checking 
etc...)

But what immediately formed in my mind after reading the wiki on 
RaaSucc  ( http://www.rubygarden.org/ruby?RaaSucc ) was the following.

Have a web interface for maintainers of a packge to submit packages 
and any metadata associated with it. Store this information in the 
database. Have the client tool communicate with a "package getting" 
servlet type of thing (WEBrick has a servlet paradigm). The servlet 
will query the database and return you a list of packages to get 
(this would include any amount of dependencies). After that the 
client tool will go through the packages, getting them, unpackaging 
them, and finally setting them up and running tests.

I could be completely overlooking the obvious as I try to think of 
the simplest thing that would possibley work, but why do you need a 
dependency generator?

- -- 
Signed,
Holden Glova
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8JnDo+mF116Lw2cQRAueFAJ4zyuFQdsEMXKaBfIlgOYv5VMmkAwCeJ+/z
FFzrmWo1bIivvUjAhOvyyZU=
=FQHF
-----END PGP SIGNATURE-----