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

Re: Feature request: SubWCRev if not inside a working copy

From: Gingko <from_tigris_at_nospam.homelinux.org>
Date: Tue, 20 Oct 2009 01:10:17 +0200

----- Original Message -----
From: "Stefan Küng" <tortoisesvn_at_gmail.com>
To: <users_at_tortoisesvn.tigris.org>
Sent: Monday, October 19, 2009 9:57 PM
Subject: Re: Feature request: SubWCRev if not inside a working copy

> Sorry, but that's not the job of SubWCRev. It has to throw an error in
> case you're using it on an unversioned folder.
> But you can change your script to catch that error and then either write
> default values to your version file, or copy a template version file to
> the destination.
> SubWCRev is a tool with a specific purpose. If you want to do more with
> it, you have to do that in your own script.
> Stefan

There is an utility that comes with command line Subversion clients which is
called "svnversion".

If you run it as a command line utility, it outputs a string on its standard
output that includes the last SVN revision number.

If you run it outside a working copy, it only outputs the string "exported",
without producing any error.

I use that in another project, but as "svnversion" doesn't process
templates, it needs a lot of intermediary processing before achieving the
desired result (and also, it makes Subversion being an additional
prerequesite for building the project).

I expected using SubWCRev in order to configure something largely simpler.

Unfortunately, this lack of the "not working copy" default behaviour that
exists in "svnversion" will not make things as simple as I was expecting.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-20 02:40:50 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.