[Phpwm] Version control - project organisation

David Goodwin david at codepoets.co.uk
Fri Aug 28 08:25:24 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I have a product which, like any other, get upgraded over time and new  
> releases (tags) are made.  Some clients use the "standard" version,  
> but they'll almost certainly require customisation to a couple of  
> files.  E.g. language terminology and a logo:
> 
> 	/lang/en_GB.php  *
> 	/public/images/logos/company-logo.png

I'd have been tempted to solve the problem through include_path magic -
i.e. have an svn:externals which points to the common code used by all
sites. Then have a 'local changes' dir, which is before the
svn:externals link in the include path... so if you effectively have a
subset of the common files locally which contain changes.

Failing that, you could do something like OXIDCart - whether this is a
good idea or not is a different matter - see e.g.
http://www.frontalaufprall.com/2009/08/27/extension-terror/

David.
- --
David Goodwin

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqXlAwACgkQ/ISo3RF5V6Z50QCghv3RGgTwfOPx3CUAoSAKQoSa
RA4An2H/F7lkuQonV5N2DVeMz1DjvgOZ
=5S1B
-----END PGP SIGNATURE-----



More information about the Phpwm mailing list