> Lorenz wrote:
>>>>> I'm trying to add a file to a tag, which isn't and never should
>>>>> be under
>>>>> version control in my working copy.
>>>>> [...]
>>> If you don't mind adding a new directory to hold this new file you
>>> could 'svn import' it after creating the tag, but you would be
>>> violating several typical subversion conventions in the process.
>> the only convention that come to my mind is 'don't modify tags'.
>> What other conventions do you think off?
>
> Normally you expect tags to be an exact copy of some other path in
> the repository or a workspace at some point in time. Also you
> expect them to appear atomically so other users or automated tools
> will either see a complete tree or no tag at all.
>
>> And regarding 'don't modify tags': I wouldn't consider adding a file
>> to complete the tag as modification.
>
> If you want the tag to represent your workspace state you can create
> it from there instead of a repository url - but you have to be
> careful to commit everything that belongs back in the branch/trunk
> path first. It can be confusing to have things in tags with no
> repository history elsewhere.

Agreed, that can be confusing, but now I tag from working because of
just the kind of scenario described by the OP.

Back in my early days with SVN, when I was more pedantic, I made a
branch first, made the necessary change(s) and then used svn mv to
make the branch into a tag. This is "clean" from the perspective of
tags being immutable. It does produce a messier repo history though.