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

Re: versioning rant

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-02-21 00:49:39 CET

On Wed, Feb 20, 2002 at 06:27:58PM -0500, Perry E. Metzger wrote:
>
> Greg Stein <gstein@lyra.org> writes:
> > It's something that we can't do either :-)
> >
> > A given executable can be built from a multi-revision working copy. There
> > isn't a way to say "this is exactly revision 1347". It might have parts from
> > revision 1204, for example.
>
> Speaking from NetBSD (and I'm concerned about making sure NetBSD can
> use Subversion), we need to be able to identify the revisions of the
> files that built an executable. That also implies, by the way, that we
> need to know which branch and revision the version comes from since
> subversion has only the one revision for the entire repository, thus
> Wednesdays 1.5 branch and trunk would have the same revision number.
>
> When I say "need", I mean "need". I have to be able to figure out what
> someone is running.

i've been thinking about this, and it seems like a problem best solved
with keywords.

perhaps a $RepositoryPath$ keyword that expands to the file's actual
path in the repository, which would show you what branch/tag it's on.

actually, we already have a $URL$ keyword, which looks like it would
expand to what we want. you combine that with the $rev$ keyword and
you can have something in each file that uniquely identifies what
version and what branch it came from.

-garrett

-- 
garrett rooney                     Unix was not designed to stop you from 
rooneg@electricjellyfish.net       doing stupid things, because that would  
http://electricjellyfish.net/      stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:09 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.