[Gforge-devel] Commit policy?

Roland Mas lolando at debian.org
Fri Oct 6 03:09:26 EDT 2006


Michael Casadevall, 2006-10-05 15:39:54 -0400 :

> [...] To compound the problem, changes involving the database are a
> pain, mostly because you need to know what patch files to apply to
> the database to just get it installed from CVS. The best solution
> here would be some sorta intelligent upgrade that can apply the
> changes per each checkout - Mediawiki uses something like that.

I had missed that on the first reading.  This problem has been known
and solved already, see the db-upgrade.pl script.  It's not
particularly intelligent: it stores a database schema version in a
designated table, and only applies SQL changes from the last installed
version to the current one.  It's solid and has worked for years,
though.

Roland.
-- 
Roland Mas

'And what would humans be without love?'
RARE, said Death.  -- in Sourcery (Terry Pratchett)


More information about the Gforge-devel mailing list