[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Is there some keyword providing the local path within the working copy?

From: Balogh Péter <balogh.peter_at_xcite.hu>
Date: Thu, 25 Jan 2018 21:45:36 +0100

On 2018-01-25 20:40, Johan Corveleyn wrote:
> On Thu, Jan 25, 2018 at 4:55 PM, Thorsten Schöning
> <tschoening_at_am-soft.de> wrote:
>> Hi all,
>> I'm distributing software directly using SVN and the working copy
>> contians a configuration file which needs to contain some absolute
>> path to a special dir in that working copy. The goal is to not need to
>> commit that path of course, but automatically generate it during a
>> checkout/update. I had a look at the new custom kewords in SVN 1.8[1]
>> already, but didn't find any local working copy related path.
>> So, is there such a local working copy path available and I only
>> didn't find it yet?
>> If not, any plans to provide such a path I didn't find yet? I was not
>> even able to find discussion in that direction, but doubt I'm the
>> first one with such question.
>> Thanks!
>> [1]: http://svnbook.red-bean.com/en/1.8/svn.advanced.props.special.keywords.html
> Yes, you're the first one asking for this, AFAIK :-).
> But I don't understand what you're trying to do. You want to include
> the WC-root-relative path to *another dir* inside some config file,
> while you're checking out or updating that config file? That's weird.
> The keywords in SVN are only able to include information that's
> directly related to the file in question, not information about
> another file or dir.
> But regardless, this sounds to me more like something you should solve
> with a build script or somesuch ...

I think this use case is similar to ours, the way we solved it, was
adding a config file one directory above the svn root folder, that's not
If subversion supported post checkout / update command execution in the
client side, or if a tracked file could be excluded from commit changes
on the client side, much better solutions could be implemented in our
case as well
One alternative that we've considered was generating the config file
when the application starts, and ignoring it by name, but we have not
implemented this

I hope this helps

Best regards,
Received on 2018-01-25 21:45:53 CET

This is an archived mail posted to the Subversion Users mailing list.