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

Re: post-update hook?

From: Jan Hendrik <jan.hendrik_at_bigfoot.com>
Date: 2004-06-03 12:30:55 CEST

Concerning Re: post-update hook?
m christensen wrote on 2 Jun 2004, 7:04, at least in part:

> Jan Hendrik wrote:
> >I am on the way to have the contents pages in web projects here
> >created automatically by a script from versioned datafiles (currently
> > contents are static, versioned HTML files). This script shall be
> >invoked i. a. by a post-commit or even start-commit hook.
> >
> >I don't want to put the automatically generated contents under
> >version control, but I would like having them updated in working
> >copies on svn update. Is there something like a post-update hook?

> I guess my question is why NOT place them in the repository.
> They are part of your build process.

Nope. IMHO generated files have lost nothing in the version
system. If I would do this on the webserver they would not even
exist in local (working) copies. But just think about including such
files: you have 200 items in a master contents list that a script
splits up into 20 files with 10 items each (similar to search results
in Google). Now you add one item at the beginning of the master
list - this will result in all 20 files being recreated as this new item
shifts all following items one step forward. Result: 20 files have to
be committed. Not once a week, but at least once per day by
each of the developers. And now we have contents lists in several
languages which multiplies things ...

> You want them checked back out as a set with the other files.
> they should be tested as a complete set with all the other files to
> validate your code generation scheme if nothing else. It solves your
> checkout problem.

The perhaps cleanest solution would be running a script on the
webserver that produces the contents lists live. I have an outline
for a PHP script that is said to do this. However, I do not know
PHP, from the PHP download page I see that Apache 2 support is
experimental only, so I would have to set up Apache 1.3 here for
testing (which our hoster runs anyway) parallel, then folks here
would have to test pages through the local development webserver
which is not supported by all editors in use here ... Everything can
be done for sure, but the nine or ten months running SVN have
caused me enough trouble and grey hair to prefer a solution with
less overhead, though less professional.

Jan Hendrik

Freedom quote:

     The house we hope to build is not for my generation but for yours.
     It is your future that matters.
     And I hope that when you are my age,
     you will be able to say as I have been able to say:
     We lived in freedom.
     We lived lives that were a statement, not an apology.
                -- Ronald Reagan

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 3 16:55:26 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.