Re: Putting the tag name in the tagged code

Because I don't 'obviously' know that information. If it's a working
directory, I could pull it out of the .svn information, sure. But if
it's a source distribution, or if I can't rely on svn, then it's a
manual process, and the whole point of the exercise is to take the
human out of the loop.

I did find a way to get what I wanted. Almost. 'svn copy <dir>
<URL>' is intended to do a branch of the working directory, not the
revision the working directory is based on. Fortunately, my
Continuous Integration tool uses this form of the command to tag
builds.

Unfortunately, it means I'm open to another class of bad tagging.
Notwithstanding that little hitch, at least the code builds as tested,
and the forensic trail is clear if something actually is amiss with
the tagging. I just have to enforce a convention not to change any
checkout artifacts in the build process. Since this is a perfectly
reasonable convention regardless, I'm not too broken up about it.

Thanks,
-Jason

On 3/5/07, Bob Hiestand <bob.hiestand@gmail.com> wrote:
> On 2/28/07, jason marshall <jdmarshall@gmail.com> wrote:
>
> > Perhaps I should also point out that I'm a library writer, so my
> > binaries go into someone else's binaries. I get bug reports from my
> > users, and from their users. It's a challenge to make sure that my
> > users are keeping up-to-date with patches, so the number of bug
> > reports are lower, so I can tell a known issue from a regression, and
> > so I don't get pulled into every end-user conversation.
>
> When you run your build process, or use a task in your process to
> extract the tree, you obviously know which branch/tag you're building.
> Why not generate an unversioned file in your sandbox at that point
> and use it during builds?
>
> Thank you,
>
> Bob
>

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