Am Donnerstag, 20. August 2009 14:51:08 schrieb Andreas Gruenbacher:
On Thursday 20 August 2009 14:24:14 Luke Imhoff wrote:
Our internal tools use osc as a library, so the client side change would hopefully be transparent.
That would depend on the features that your tools rely on, and how much effort is put into osc in order to preserve the same work flow. (For example, osc is based around the model that all commits are sent to the server immediately, while git allows to work "offline" for a while and sync back / push changes in batches.)
Dunno how important that is for OBS, since you need anyway a server to be able to build the packages, also locally. (a local OBS instance would solve the problem though).
I'd just stress that the backend migration tools must be very good so that people running local instances can migrate easily too or moving away from bsdb to git as a community could prove problematic.
I agree. Migrating packages with several levels of source links becomes somewhat complex, but the existing git frontend already requires all this functionality; there is little left to do other than pushing the resulting git repository to the backend. This should give us good confidence that the conversion works well.
And I would like to see first how you intend to do the permission checking (for write permissions as we have it now and for upcomming read permissions). This comes together to the feature that our current server is storing files (esp. the large tar balls) once, even when another user creates the same package with same tar ball at a different place and with different permissions. Without an idea for a solution here I see no way to move away from it. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org