[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [RFC] Design of svnvendor.py

From: John Peacock <jpeacock_at_rowman.com>
Date: 2006-05-19 18:04:13 CEST

Giovanni Bajo wrote:
> Did you read it the design document through?

No, I read your first paragraph about how difficult you find vendor
imports and that is what I am responding to. I was merely pointing out
that vendor imports don't have to be difficult.

I have no special interest in your tool, which is way too "this is the
way *we* do things" specific for my taste. You want to add all sorts of
syntactic sugar which makes your chosen tool easier for *your*
developers to handle. In my opinion, and that very carries little
weight in this project as I am only a peripheral developer, this tool is
far too dedicated to one particular (and I would even say very narrow)
methodology to belong in the Subversion distro. YMMV.

Now on to the specific comments you made:

> This does a new import of the vendor, so it's not answering my concern.

Actually, if you read the example on the elixus.org page, you'll see
that the command I cited was exactly the same for every single vendor
import. The import is targeted at the same "current" path every time
and SVK does the right thing.

> The problem I'm thinking of is the following:

I'll assume that I am in a working copy that is anchored in the project
root folder, e.g. //project, so we don't have to worry about paths, and
run commands which will do what I think you mean.

> 1) svk import of libcomplex 1.1

   $ svk import -m 'libcomplex-1.1' ./current ~/path/to/libcomplex-1.1
   $ svk cp -m 'libcomplex-1.1' ./current ./tags/libcomplex-1.1

> 2) svk cp: use 1.1 in my project

   $ svk cp -p ./tags/libcomplex-1.1 ./local/trunk

(you could also copy from ./current, but this make a little more sense
from a history standpoint).

> 3) svk import of libcomplex 1.2

   $ svk import -m 'libcomplex-1.2' ./current ~/path/to/libcomplex-1.2
   $ svk cp -m 'libcomplex-1.2' ./current ./tags/libcomplex-1.2

> 4) svk smerge: upgrade to 1.2 in my project

   $ svk smerge -C ./tags/libcomplex-1.2 ./local/trunk

#if no conflicts

   $ svk smerge ./tags/libcomplex-1.2 ./local/trunk

> Now, how can I get back to version 1.1?

   $ svk smerge -c ./tags/libcomplex-1.1 ./local/trunk

#if no conflicts

   $ svk smerge ./tags/libcomplex-1.1 ./local/trunk



John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 19 18:04:22 2006

This is an archived mail posted to the Subversion Dev mailing list.