You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@subversion.apache.org by "j.j.green" <j....@shef.ac.uk> on 2006/12/13 21:50:20 UTC

Get tag (not revision) into C & perl programs

Hi

I'm a recent refugee from PRCS and am kind of stuck on a problem.
PRCS has major/minor version keywords which I can get into my 
programs easily:

  /* $Format: "#define PROJECT_VER_MAJ $ProjectMajorVersion$" $ */
  #define PROJECT_VER_MAJ 5
  /* $Format: "#define PROJECT_VER_MIN $ProjectMinorVersion$" $ */ 
  #define PROJECT_VER_MIN 39

and then I have my programs print 

  This is program (version 5.39)

when they operate verbosely. I get that for subversion I need to use 
tags to hold the human-readable release-version, and these are 
disconnected from the revision. I guess that I will need to do some 
scripting in order to get a release version  into my C & perl programs.  
Im thinking a script that 
 - pulls a release-version.txt file from the repository
 - read and increments the version in that file to "5.30"
 - checks the file back in
 - checks out a C header and writes the release-version as a #define RELVER
5.30
 - checks the file back in
 - creates the tagged release as tags/program-5.30

This is OK for C. But I have around 60 perl programs which use the same
PCRS mechanism:

  # The version: $Format: my "\$version = \"$ProjectVersion$\";"$
  my $version = "5.39";

So this is going to get cumbersome. I've searched around but can't find
a slick way to do this. I've seen the FAQ on getting the revision into C,
but I'm after insertng the *tag*

I'd be most grateful for suggestions

Jim

-- 
View this message in context: http://www.nabble.com/Get-tag-%28not-revision%29-into-C---perl-programs-tf2816911.html#a7862119
Sent from the Subversion Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Get tag (not revision) into C & perl programs

Posted by Talden <ta...@gmail.com>.

On 12/15/06, Andy Levy <an...@gmail.com> wrote:
> On 12/13/06, j.j.green <j....@shef.ac.uk> wrote:
> >
> > Hi
> >
> > I'm a recent refugee from PRCS and am kind of stuck on a problem.
> > PRCS has major/minor version keywords which I can get into my
> > programs easily:
> >
> >   /* $Format: "#define PROJECT_VER_MAJ $ProjectMajorVersion$" $ */
> >   #define PROJECT_VER_MAJ 5
> >   /* $Format: "#define PROJECT_VER_MIN $ProjectMinorVersion$" $ */
> >   #define PROJECT_VER_MIN 39
> >
> > and then I have my programs print
> >
> >   This is program (version 5.39)
> >
> > when they operate verbosely. I get that for subversion I need to use
> > tags to hold the human-readable release-version, and these are
> > disconnected from the revision. I guess that I will need to do some
> > scripting in order to get a release version  into my C & perl programs.
> > Im thinking a script that
> >  - pulls a release-version.txt file from the repository
> >  - read and increments the version in that file to "5.30"
> >  - checks the file back in
> >  - checks out a C header and writes the release-version as a #define RELVER
> > 5.30
> >  - checks the file back in
> >  - creates the tagged release as tags/program-5.30
> >
> > This is OK for C. But I have around 60 perl programs which use the same
> > PCRS mechanism:
> >
> >   # The version: $Format: my "\$version = \"$ProjectVersion$\";"$
> >   my $version = "5.39";
> >
> > So this is going to get cumbersome. I've searched around but can't find
> > a slick way to do this. I've seen the FAQ on getting the revision into C,
> > but I'm after insertng the *tag*
> >
> > I'd be most grateful for suggestions
>
> Unlike CVS and some other version control systems, tags in Subversion
> are nothing more than copies. The "difference" is in the significance
> that the user applies to the contents/names in the tags directory.
>
> So, if you want to do this, I think you're looking at doing some
> path-reading and parsing to update the file contents.

For any folder intended solely to be a container for tags or branches
you could set a property indicating it's role.

A script could then walk up to find if it's in a tag or branch...
otherwise it's in the trunk

EG "folder_type" and values "tags_container" or "branches_container"

so in

.../
  tags/
     releases/
     milestones/

releases and milestones would have the property "folder_type" set and
interrogating it would show if it's a tag or a branch.  Of course to
populate the file with this information you do still need to write a
script to walk the path interrogating SVN and do token replacement in
the file.

Using this mechanism, identifying if it's a release or a milestone is
equally simple.

--
Talden

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Get tag (not revision) into C & perl programs

Posted by Andy Levy <an...@gmail.com>.

On 12/13/06, j.j.green <j....@shef.ac.uk> wrote:
>
> Hi
>
> I'm a recent refugee from PRCS and am kind of stuck on a problem.
> PRCS has major/minor version keywords which I can get into my
> programs easily:
>
>   /* $Format: "#define PROJECT_VER_MAJ $ProjectMajorVersion$" $ */
>   #define PROJECT_VER_MAJ 5
>   /* $Format: "#define PROJECT_VER_MIN $ProjectMinorVersion$" $ */
>   #define PROJECT_VER_MIN 39
>
> and then I have my programs print
>
>   This is program (version 5.39)
>
> when they operate verbosely. I get that for subversion I need to use
> tags to hold the human-readable release-version, and these are
> disconnected from the revision. I guess that I will need to do some
> scripting in order to get a release version  into my C & perl programs.
> Im thinking a script that
>  - pulls a release-version.txt file from the repository
>  - read and increments the version in that file to "5.30"
>  - checks the file back in
>  - checks out a C header and writes the release-version as a #define RELVER
> 5.30
>  - checks the file back in
>  - creates the tagged release as tags/program-5.30
>
> This is OK for C. But I have around 60 perl programs which use the same
> PCRS mechanism:
>
>   # The version: $Format: my "\$version = \"$ProjectVersion$\";"$
>   my $version = "5.39";
>
> So this is going to get cumbersome. I've searched around but can't find
> a slick way to do this. I've seen the FAQ on getting the revision into C,
> but I'm after insertng the *tag*
>
> I'd be most grateful for suggestions

Unlike CVS and some other version control systems, tags in Subversion
are nothing more than copies. The "difference" is in the significance
that the user applies to the contents/names in the tags directory.

So, if you want to do this, I think you're looking at doing some
path-reading and parsing to update the file contents.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Get tag (not revision) into C & perl programs

Posted by Martin Scharrer <ma...@madmarty.de>.

Hi,

On Wednesday 13 December 2006 22:50, j.j.green wrote:
> This is OK for C. But I have around 60 perl programs which use the same
> PCRS mechanism:
>
>   # The version: $Format: my "\$version = \"$ProjectVersion$\";"$
>   my $version = "5.39";

> I'd be most grateful for suggestions
If you just like to have the project version coded as tag, i.e. it's SVN URL 
looks like this:
     svn://host/project_name/tags/version5.39/...
(Protocol could vary)
then just do something like this:

Set the svn:keywords property to 'URL' to include the URL and write something 
like this into your Perl scripts:

my $version = ( '$URL$' =~ m{/tags/version(.*?)/} && $1 );
or 
(my $version = '$URL$') =~ s{.*/tags/version(.*?)/.*}{$1};
or
my $version = ( '$URL$' =~ m{/tags/version(.*?)/} ) ? $1 : undef;

The $URL$ is of course expanded in your Perls script.

Drawbacks:
 - You need a consistant tagging system
 - Works only if you build the checked-out tagged version not a branch or the 
trunk

I hope this helps you,
Martin

or some 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn:externals problem in checkout

Posted by Bob Hiestand <bo...@gmail.com>.

On 12/14/06, LIRA Olavo <Ol...@gemalto.com> wrote:
>         Fetching external item into 'EEBXXX_YYYZZZ\Dev'
>         svn: 'EEBXXX_YYYZZZ\Dev' is already a working copy for a
> different URL
> -----------
>
>         My svn:externals is: "Dev/ https://repository/trunk/toto"
>
>         Where directory Dev already exist in project A, but when I
> change the value to:
>         "Dev/temp https://repository/trunk/toto"
>         Where temp is not under SVN control, then it works fine.
>
>         Is it normal? Is there another way to avoid this kind of
> problem? Should I use something else than svn:externals for this
> situation?

Yes, the directory named by the external directive should not exist in
the current directory.  Remove the 'Dev' directory and commit, then
set the external property and update.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org