Poke. Eliott- would you be willing to work on the server side of this? Obviously this is no rush deal, but I feel like it would be easier to write a client tool if I knew the layout and specifics of the server side.
I'm down chief.
I think we would stick with our current abs layout: <basedir> |--core |--extra |--community |--unstable |--testing | |--core | |--extra | |--unstable | |--community (ok, not yet, but in the future) |--PKGBUILD.proto |--proto.install |--local (empty directory)
I don't know if it would need to be laid out like this on the server (it isn't now, but that is csup), but it would probably be in our best interest if we limited rsync connections to one per abs fetch.
It would be optimal (read: easiest) if we could just rsync for the whole tree..one config stanza. That might require a bit more work on the checkout client thing (that will populate the server side rsync dir). Not sure..