SubWCRev - enhancement proposal

[Jens Geyer]

Hi there,

I'm right now playing around with the SubWBRev tool and fould it very
useful. Nice work!

While doing that, I wonder if it would be a good idea to allow replacing
template keys with values from environment variables through
SubWBRev.exe?

The reason is, that I would like to have the WC revisions and the
current date+time (which SubWBRev does) and the name of the build
project, which is given as environment variable on the build server. And
instead of writing another tool that processes the output of SubWBRev
any further, it would be nice if all these replacements could be done
with the same tool.

What do you think?
Or do I just overlook something?


Best regards,
Jens Geyer (VSX)

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2412974

To unsubscribe from this discussion, e-mail: [dev-unsubscribe@...].

[Stefan Küng]

Jens Geyer wrote:

> Hi there,
>
> I'm right now playing around with the SubWBRev tool and fould it very
> useful. Nice work!
>
> While doing that, I wonder if it would be a good idea to allow replacing
> template keys with values from environment variables through
> SubWBRev.exe?
>
> The reason is, that I would like to have the WC revisions and the
> current date+time (which SubWBRev does) and the name of the build
> project, which is given as environment variable on the build server. And
> instead of writing another tool that processes the output of SubWBRev
> any further, it would be nice if all these replacements could be done
> with the same tool.
>
> What do you think?
> Or do I just overlook something?

Well, that could be done without too much work. But I don't like the
idea - it would be something that SubWCRev isn't really designed to do,
it's not its intended purpose.

In our very own build (TortoiseSVN) we need to do some string replacing
in certain files to make the build work (some libraries otherwise fail
to build properly because they're not aware that we're past the year
2000 and VC6 isn't in use anymore). But we don't use SubWCRev for this
but use the NAnt script to do it. I think that's the better way to do
it: use the right tool for the right job.

Stefan

--
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2413280

To unsubscribe from this discussion, e-mail: [dev-unsubscribe@...].

[Jens Geyer]

Hi Stefan,

I accept you answer, although the argument is questionable:  It depends on the definition of "job".

:-)

Thanks anyway,
JensG


 
-----Ursprüngliche Nachricht-----
Von: Stefan Küng [mailto:tortoisesvn@...]
Gesendet: Samstag, 31. Oktober 2009 19:16
An: dev@...
Betreff: Re: SubWCRev - enhancement proposal

Jens Geyer wrote:

> Hi there,
>
> I'm right now playing around with the SubWBRev tool and fould it very
> useful. Nice work!
>
> While doing that, I wonder if it would be a good idea to allow replacing
> template keys with values from environment variables through
> SubWBRev.exe?
>
> The reason is, that I would like to have the WC revisions and the
> current date+time (which SubWBRev does) and the name of the build
> project, which is given as environment variable on the build server. And
> instead of writing another tool that processes the output of SubWBRev
> any further, it would be nice if all these replacements could be done
> with the same tool.
>
> What do you think?
> Or do I just overlook something?

Well, that could be done without too much work. But I don't like the
idea - it would be something that SubWCRev isn't really designed to do,
it's not its intended purpose.

In our very own build (TortoiseSVN) we need to do some string replacing
in certain files to make the build work (some libraries otherwise fail
to build properly because they're not aware that we're past the year
2000 and VC6 isn't in use anymore). But we don't use SubWCRev for this
but use the NAnt script to do it. I think that's the better way to do
it: use the right tool for the right job.

Stefan

--
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2413280

To unsubscribe from this discussion, e-mail: [dev-unsubscribe@...].

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2413759

To unsubscribe from this discussion, e-mail: [dev-unsubscribe@...].

[Stefan Küng]

Jens Geyer wrote:
> Hi Stefan,
>
> I accept you answer, although the argument is questionable:  It depends on the definition of "job".

My definition of "job" is "what it's designed to do".
Otherwise we'll end up with a swiss army knife like this one:
http://www.geekologie.com/2006/08/25/incredible_knife.jpg

Also reminds me of my former boss. He needed a "Messtechniker", but
instead ended up hiring a "Messetechniker". You can maybe now imagine
how thoroughly he read the applications and how he interviews the
applicants :)
It's all in the job title and job description :)

Stefan

--
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2414361

To unsubscribe from this discussion, e-mail: [dev-unsubscribe@...].