On Thursday 25 September 2008 22:46:45 wrote Archie Cobbs:
On Thu, Sep 25, 2008 at 3:39 PM, Adrian Schröter <adrian@suse.de> wrote:
On Thursday 25 September 2008 21:58:22 wrote Archie Cobbs:
The "how to verify and fix broken links?" thread brought up a question I've always wondered about....
Why does osc not-exactly-duplicate the functionality of svn, instead of just letting the user use svn directly?
In other words:
- Use svn for all checkout, diff, commit, merge, etc. operations
svn has no functionlity for source links for example. So all the derived versions would not be possible and manual work would be always needed, not only when conflicting changes exist.
What do you mean by source links functionality? Clearly svn can't do "osc up -e"... so that particular functionality would have to remain part of osc.. But wouldn't it still be possible to use svn for the stuff svn can do?
Apologies if I'm missing something...
It would make sense to use svn to handle the conflicts, if this modular enough in svn. But it does not make sense to introduce a protocoll wrapper or something alike. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org