I'm forwarding this from the caos mailing list, just in case anyone is interested in this "shipper" project idea... Don't know anything about it, or if it would be of interest to FL, but thought I'd post it in case it is of interest... Most of the message is edited out (via a [...] cut); just the interesting part is left. Eric ---------- Forwarded message ---------- Date: Sat, 10 Jan 2004 05:36:42 -0500 From: Eric S. Raymond <esr@xxxxxxxxxxx> To: R P Herrold <herrold@xxxxxxxxxxxx> Cc: cAos mailing list <caos@xxxxxxxxxxxxxxxx> Subject: Re: Invitation to ESR Re: fedora-d-rh] Re: RPM submission procedure [...] > - seek upload priv's (which will be granted forthwith) > - transfer in a SRPM > rsync <srpm> <userid>@temple.caosity.org::<userid> Ah, now this is why it's interesting. I'm in the throes of writing a program called 'shipper', a shipping agent for open-source releases. The idea is that you tell it about channels you want to release to, and it then does the mechanics of building RPMS, uploading, mailing notifications, posting announcements, etc, all driven by the contents of the project specfile. Push one button, your release gets shipped everywhere. Presently I have three kinds of channel defined; generic website, generic FTP site, mailing list. Also three kinds of hardwired or public channel -- ibiblio.org, redhat incoming, and freshmeat.net. Each channel type "knows" not just about a transport method but about what subset of the potential deliverables it wants -- for example, LSMs only go to ibiblio. Sounds like cAos will make a good testbed for a fourth generic channel type, an rsync channel that takes SRPMs only. -- <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> _______________________________________________ cAos mailing list cAos@xxxxxxxxxxx http://www.caosity.org/mailman/listinfo/caos ----- End forwarded message ----- -- Eric Rostetter The Department of Physics The University of Texas at Austin Why get even? Get odd!
