Simon Large wrote:
>> And I find it counter-intuitive in my environment, which is why I
>> started the discussion.
> What is counter-intuitive about it? What did you expect it to do? Maybe
> it could be made to work so that the source file is modified in some
> way, but it would be much harder to do, and what would your gain from
For example I want to hook SubWCRev in as a Pre-Build event in Visual Studio.
If I want to integrate SubWCRev with the VS integrated build system as
it is now, I'll have to make some abomination of scripts that on
pre-build runs a SubWCRev and moves some files around to replace the
original source file with the SubWCRev replacement, and when the build
finishes move the files around again. *If* the build finishes. And
I'll be really mad when it doesn't and I have to go through all my
source files and replace back numbers with $WCREV$ and such :-).
Especially if I've missed that the post-build script didn't run for
some reason, and I've later modified a lot of code and checked in and
compiled and released. Then I'll be mad.
>>>> I come from a VS.Net / NetBeans etc. world where builds are done
>>>> with the click of a button in the GUI, and SubWCRev doesn't lend
>>>> itself to this way of working very easily. The Subversion way of
>>>> doing keywords work better there.
>>> But the SVN substitution is done at update time so it won't find
>>> local mods made after that. You have to run a program at the time
>>> you want to make that check.
>> At commit also, no?
> Well OK. But what if you build before committing?
Hehe. Spot on. *Scratches head*.
Right, ok, in THAT case I really need SubWCRev.
For the records, I don't do that and I don't use SubWCRev for this,
but I can see how it really shines there to be able to just stuff
SubWCRev in the build chain and have it do it's magic.
Seeing as this is a good thing to do on all your projects, it would be
very neat if SubWCRev could be made to just modify the original source
files, with a single command like "SubWCRev --update", and all that
one had to remember would be to put "SubWCRev --update" in your
pre-build event in all your projects.
Dreaming a bit again, as Steve suggested I'm prone to earlier :-).
>> I'm unsure what local modifications you'd like to find and include in
>> a build that's not reflected in the repository somehow, but I'll go
>> read the docs again.
> Some people (including me) use it in their build scripts for exactly
> that reason. We _don't_ want to release uncommitted code by mistake, and
> using SubWCRev helps show that condition up. It is all too easy to
> commit changes and then forget to redo the build before making the
I need to go look up in the docs what SubWCRev puts in instead of a
revision if there is local modifications. Never actually saw it
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Apr 9 21:46:49 2005