Re: cdbs?? Why?
Gonéri Le Bouder wrote:
> Le dimanche 16 juillet 2006 21:46, Jon Dowland a écrit :
>> At 1152945721 past the epoch, Reinhard Tartler wrote:
>> > IMO, it obfuscates things, makes managing
>> > patches with svn hard to impossible
> Can you please explain more precisely where the problem is?
I tried to explain it in another post in this thread. Let me rephrase
it:
IMO, a SCM (source code managment system) is a tool to manage a line of
development (let's call that 'branch'), and you can get from each step
(let's call this 'revisions') to another by applying patches.
svn does a pretty good job doing this, and personally, I think it is the
best central SCM I've seen so far [1]. You can create, apply and
review patches directly in SVN. Why should we duplicate this use case by
managing patches with another SCM (may it be dpatch or custom patch
helper scripts)?
The only valid reasoning I've seen so far is that several people work on
a package, and some refuse to use svn, and insist on using another SCM,
or just use svn to put some files in a common place, degrading svn to
some sort of 'file shareing tool'.
Greetings,
Reinhard
[1] sidenote: I personally prefer decentral SCM, but that doesn't matter
here. I've been thinking about converting some branches to bzr using
tailor. [2, 3] This of course doesn't work with 'mergeOnUpstream'
branches. One other reason why I'm against using it, even when it
requires more bandwith for uploading.
[2] http://www.darcs.net/DarcsWiki/Tailor
[3] http://www.darcs.net/DarcsWiki/ConvertingFromSubversion
Reply to: