cvs vs svn...

[Paweł Sakowski]

On Sat, 2005-09-10 at 02:59 +0200, Tomasz Pala wrote:
> I don't get it. Why is:
> 
> cvs ci SPECS/foo.spec SOURCES/foo.patch
> 
> worse than the same in svn?

Because it won't work with cvs unless you add -d$(cat SPECS/CVS/Root) :P

BTW, that's another reason for directory-per-package. With SPECS/SOURCES
there's no straightforward way to make sure that you're committing
everything you've changed. Consistent (+-) file naming lets you use the
result of `cd SOURCES;cvs up foo*` as a clue, but 1) it will give some
false positives (e.g. glibc* for glib) and some false negatives (eg.
sysvinit-paths.patch for SysVinit) and 2) you won't see deleted files.
OTOH in a package's directory a simple `svn status` guarantees that
"oops, forgot to commit this other patch" won't happen.

-- 
Paweł Sakowski <saq at pld-linux.org>
PLD Linux Distribution