[Tracker-discuss] [issue44] Set up python-dev tracker
Erik Forsberg
forsberg at efod.se
Sun Jan 14 17:49:23 CET 2007
As part of issue54, I upgraded the templates to match those of roundup
1.3.2. This brought in some degermanization, more specifically the
problem pointed out in msg227 and msg320 should be gone.
While I were at it, I also made some changes in how the roundup
installation is done. There is now a 'roundup-src' directory under
tracker/ in svn. Currently, it contains a copy of
tracker/vendor/roundup/current, which is roundup 1.3.2.
It is checked out under psf:/home/roundup/src/, and the roundup from
that directory was then installed using 'python setup.py install
--prefix=/home/roundup/roundup-production'. The symlink
/home/roundup/roundup was then adjusted to point to
/home/roundup/roundup-production.
The idea is that this way, we can keep our own adjustments to roundup,
such as the one proposed in msg298 of issue68, under svn control in
tracker/roundup-src. Whenever there's been a change there, we can run
a new 'python setup.py install
--prefix=/home/roundup/roundup-production' and get the new version in
place.
When there's a new roundup version in place, we'll do the usual vendor
branch dance to merge in changes between the old and the new roundup
version into tracker/roundup-src.
I think this is a good way to do it, but other ideas are welcome. In
practice, this means no change for any scripts, as ~roundup/roundup
still points to the production roundup instance.
Cheers,
\EF
--
Erik Forsberg http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
More information about the Tracker-discuss
mailing list