--HRdhlg6t9GwInNtW8bi
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2003-06-13 at 11:06, Brett H. Williams wrote:
> # ruby-package-get syck
> RPM detected -- building packages.
> Downloading package list from RAA..... done.
> Finding syck.... done, 2 prerequisites.
> Downloading syck.... done
> making spec files.... done
> + rpmbuild -ba prereq1.spec
> .....
> + rpmbuild -ba prereq2.spec
> .....
> + rpmbuild -ba syck.spec
> RPMS are in ~/rpm/RPMS. Installing....
> + rpm -i ~/rpm/RPMS/{prereq1-0.0.0,prereq2-0.0.0,syck-1.0}.noarch.rpm
> Done!
> 
> 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...

I was actually starting to thing about adding this sort of feature. In
my case I was thinking it would probably be quite easy to generate
gentoo ebuild files - although I had considered running over the entire
repository and generating all the ebuilds, so that everything becomes
accessible from emerge (the gentoo package installer).

Doing it live is also possible (and may even be better).

I don't have much experience building RPMS, but if someone sent me a
template (and perhaps a walkthrough of the steps) I would be happy to
experiment with including this feature in raa-install.

-Tom


--HRdhlg6t9GwInNtW8bi
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA+6f2fnQF3llOblFkRAswiAJ4nl/sd7uY75WoVNpOlnqNvrOPFfQCeK05J
AkqQCtJTeTvPj0rpstUFSKslB
-----END PGP SIGNATURE-----

--HRdhlg6t9GwInNtW8bi--