-----BEGIN PGP SIGNED MESSAGE-----
On Monday 11 May 2009, Jeff Johnson <email@example.com> wrote:
> FYI: Ralf Engelschall did almost all the work setting up @rpm5.org.
> All I did was say "Sure!" when asked.
In this case: Sorry to you, Ralf, that I didn't give you the credit you
deserved. *bow* :-)
> And sure, rpmbuild2 or anything else could be done @rpm5.org.
> The more interesting question is what is "useful".
> Building software and producing *.rpm packages is more or less routine,
> an already solved problem. Sure there are bugs/quirks, but there's
> a slew of *.rpm packages around.
Thing is that you're right that *.spec files are a grown build recipe. You
(?) have already done much to weed out irregularities like the old rpmrc
files, but the macro concept could be followed more esplicitly. You also
said that the *.spec files sooner or later are going to need a real grammar
that backs the syntax up, and since the the files are already some kind of
macro/meta language, this is probably a good idea.
> What appears to be more interesting these days is how to construct
> a "build factory", like OpenSUSE (there are several other efforts
> around, OpenSUSE is just the most visible and perhaps the most advanced).
This could probably become a sister project @rpm5.org on top of RPM itself.
> Well on odd days I loathe RPM, and on even days I kinda like RPM still.
A mod-2 mood, I see. :-)
> Dunno if there is "potential" left with RPM itself, we'll see. The
> types of interesting/useful problems today are very different than
> when RPM was first written in 1997.
Yes, there still is. One of the highlights of RPM is that it reliably packs
software. It reliably takes care of dependencies. I don't know any other
software at which I can just throw a buch of perl modules and get my
dependencies figured out nicely. The dependency generators alone are
something that might sill have potential. (No, I didn't forget I wanted to
contribute a ruby depgen, I still want to!) I am currently working at a
cluster project @ IBM, and one of the obstacles we have is to figure out how
we can reliably keep one consistent set of stoftware (-versions) on all
nodes. I cannot imagine a clustered emerge or clustered dpkg, but a crpm,
that I can. Perhaps that's just fool's talk, but I seldom come across a
piece of software that provides so useful again and again in my
distributor's/packager's everyday life.
Gee, enough fawned. ;^)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
Received on Mon May 11 22:02:21 2009