You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "G. T. Stresen-Reuter" <te...@gmail.com> on 2008/09/22 07:53:16 UTC
Method for updating the ID on every commit
I'm wondering if someone can recommend a method for updating the ID
keyword in a file on every commit.
What I'm looking for is something akin to the "About" dialog in many
compiled programs, where they state exactly what version the code is.
Since this is exclusively for web applications, I was thinking I
could just insert the ID keyword into about.html and it would be
updated on every commit. Of course, I quickly discovered that that
wouldn't work, but the alternative: touching about.html prior to
every commit, seems unworkable.
Is there a better way?
Thanks in advance.
Gustave Stresen-Reuter
http://tedmasterweb.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Method for updating the ID on every commit
Posted by "G. T. Stresen-Reuter" <te...@gmail.com>.
On Sep 22, 2008, at 1:40 PM, Andy Levy wrote:
> On Mon, Sep 22, 2008 at 03:53, G. T. Stresen-Reuter
> <te...@gmail.com> wrote:
>> I'm wondering if someone can recommend a method for updating the
>> ID keyword
>> in a file on every commit.
>
> Keywords are expanded by the client, so there is really no method for
> doing this on the commit
>
>> What I'm looking for is something akin to the "About" dialog in many
>> compiled programs, where they state exactly what version the code is.
>>
>> Since this is exclusively for web applications, I was thinking I
>> could just
>> insert the ID keyword into about.html and it would be updated on
>> every
>> commit. Of course, I quickly discovered that that wouldn't work,
>> but the
>> alternative: touching about.html prior to every commit, seems
>> unworkable.
>>
>> Is there a better way?
>
> See the FAQ: http://subversion.tigris.org/faq.html#version-value-in-
> source
Completely understood. Thanks for the pointer to the FAQ. I suspect
I'll write a generic shell script that wraps svn export and includes
a command to insert the rev number appropriately. I was just hoping
there would be a better way, but this is good enough.
Thanks a bunch!
Gustave Stresen-Reuter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Method for updating the ID on every commit
Posted by Andy Levy <an...@gmail.com>.
On Mon, Sep 22, 2008 at 03:53, G. T. Stresen-Reuter
<te...@gmail.com> wrote:
> I'm wondering if someone can recommend a method for updating the ID keyword
> in a file on every commit.
Keywords are expanded by the client, so there is really no method for
doing this on the commit
> What I'm looking for is something akin to the "About" dialog in many
> compiled programs, where they state exactly what version the code is.
>
> Since this is exclusively for web applications, I was thinking I could just
> insert the ID keyword into about.html and it would be updated on every
> commit. Of course, I quickly discovered that that wouldn't work, but the
> alternative: touching about.html prior to every commit, seems unworkable.
>
> Is there a better way?
See the FAQ: http://subversion.tigris.org/faq.html#version-value-in-source
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Method for updating the ID on every commit
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
On Monday 22 September 2008, G. T. Stresen-Reuter wrote:
> I'm wondering if someone can recommend a method for updating the ID
> keyword in a file on every commit.
>
> What I'm looking for is something akin to the "About" dialog in many
> compiled programs, where they state exactly what version the code is.
One good way is to create releases exclusively from tagged dirs. Another way
is to use svnversion, which gives you an indicator for the revision of a
whole working copy.
Uli
--
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org