pygccxml-development

[pygccxml-development] svn rev # for release times

[Allen B. <al...@vr...>]

Roman et al:

Does anyone know where I could find the revision numbers for the various 
py++ releases?  Are there tags somewhere in the svn repository that I am 
missing.

I am trying to find this because one of my projects that had been 
working now has a code generation bug (ie. py++ generates code that 
won't compile).  I am trying to track down the specific revision that 
caused the problem so I can point at something for Roman to look at.

-Allen

Re: [pygccxml-development] svn rev # for release times

[Roman Y. <rom...@gm...>]

On 1/9/07, Allen Bierbaum <al...@vr...> wrote:
> Roman et al:
>
> Does anyone know where I could find the revision numbers for the various
> py++ releases?  Are there tags somewhere in the svn repository that I am
> missing.
>
> I am trying to find this because one of my projects that had been
> working now has a code generation bug (ie. py++ generates code that
> won't compile).  I am trying to track down the specific revision that
> caused the problem so I can point at something for Roman to look at.

Unfortunately I didn't put the tags. I don't know SVN pretty well.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/

Re: [pygccxml-development] svn rev # for release times

[Matthias B. <ba...@ir...>]

Allen Bierbaum wrote:
> Does anyone know where I could find the revision numbers for the various 
> py++ releases?  Are there tags somewhere in the svn repository that I am 
> missing.

That's not done automatically (svn cannot know when Roman does a 
release). Maybe if there's a file that only changes when a release is 
done (is there a file that just contains the version number?) then you 
could inspect the logs for that file.

> I am trying to find this because one of my projects that had been 
> working now has a code generation bug (ie. py++ generates code that 
> won't compile).  I am trying to track down the specific revision that 
> caused the problem so I can point at something for Roman to look at.

You can do an "update" on your Py++ repository and specify a revision 
number using the -r option. That way you can also go *back* with the 
revision numbers to restore an older version.
To find out what revision contains a suspicious modification you can use 
the svn browser on the SF site to inspect what has changed between 
revisions: 
http://pygccxml.svn.sourceforge.net/viewvc/pygccxml?view=rev&revision=864

- Matthias -