On 06/02/06, Dave Merrill <dmerrill@usa.net> wrote:
>
> My wc has src and dist dirs, standard I think. When I have some degree of
> "release" ready in src, I run an ant script that, among other things,
> copies
> the head revision into a temp dir outside the wc, uses SubWCRev.exe to
> insert revision info into one of the files in temp, then zips everything
> in
> temp up into a file in dist. All that remains is to commit the newly
> created
> zip file in dist, then create a copy of that dist/release state in tags.
>
> Weird part is that the revision with the updated zip that gets tagged
> isn't
> actually the one matching the revision number in the file in the zip. It
> has
> to be that way, because the dist commit is (at least) one after the commit
> it was created from.
>
> Is there any way around this? I know I want a tag of the actual distro, as
> well as the ability to create it again from sources, which seems
> inherently
> to lead to this situation. Is this process basically what others do?
How about creating the tag/branch first, export that revision and use
SubWCRev to insert the revision number into the export. Zip it up and commit
the zipped file to the tag/branch.
That also eliminates the possibility of a change (commit) slipping in
between the export and the tag/branch you do later on using your current
approach..
--
Regards,
Jean-Marc
----------------
___
// \\ @@ "De Chelonian Mobile"
/ \_/ \/._) TortoiseSVN
<\_/_\_/ / The coolest Interface to (Sub)Version Control
/_/ \_\ Check out http://tortoisesvn.org
Received on Mon Feb 6 13:20:38 2006