On Sat, Jun 14, 2003 at 12:06:05AM +0900, Brett H. Williams wrote:
> This is my biggest wish (thanks for articulating it so well, Ari).  Every
> ruby package I want to use here at work must become an RPM first.  This of
> course would be much easier if everyone used the same installer (I could
> write a script to convert the tarball into an RPM that worked for more
> than one package), but the fact remains that I have to make RPMS, someone
> else might have to make .debs, etc...

This is what I exposed in
http://www.rubygarden.org/ruby?MauricioFernandez/ThoughtsOnRaaSucc
and
http://www.rubygarden.org/ruby?MauricioFernandez/RaaSuccRequirementsEngineering

Could you tell me if the requirements in the 2nd link are realistic?
 
> I've got no idea how this sort of thing is handled in windows land.
> 
> By all means, I'm for a standard way of installing:  but really this is
> just to make it easier for me to take packages that actually play nicely
> with the system's package manager (in my case RPMs).

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

One tree to rule them all,
One tree to find them,
One tree to bring them all,
and to itself bind them.
	-- Gavin Koch <gavin / cygnus.com>