~bzr/bzr-windows-installers/2.0 : changes

~bzr/bzr-windows-installers/2.0 » Changes from revision 55

From Revision 55 to 36

Rev	Summary	Authors	Tags	Date
55	update the build script to bzr 2.0.4 update the build script to bzr 2.0.4	John Arbash Meinel	bzr-win32-2.0.4-1, bzr-win32-2.0.4-2	14 years ago
54	Use qbzr 0.14.6 Use qbzr 0.14.6	John Arbash Meinel		14 years ago
53	get the syntax right get the syntax right	John Arbash Meinel	bzr-win32-2.0.3-1, bzr-win32-2.0.3-2, bzr-win32-2.0.3-3	14 years ago
52	subvertpy now includes some scripts that we also want packag... subvertpy now includes some scripts that we also want packaged.	John Arbash Meinel		14 years ago
51	Switch to using tags for the bzr releases. Switch to using tags for the bzr releases.	John Arbash Meinel		14 years ago
50	The latest version of setuptools is 0.6.9c11, and the versio... The latest version of setuptools is 0.6.9c11, and the version specified has to match the exact version that you already have installed. The new build host got the newest setuptools version.	John Arbash Meinel		14 years ago
49	Use the new 0.3.2 version of tbzr Use the new 0.3.2 version of tbzr	John Arbash Meinel		14 years ago
48	Add the ZLIB stuff to the bdist calls. Add the ZLIB stuff to the bdist calls.	John Arbash Meinel		14 years ago
47	use docs for 2.0.2 use docs for 2.0.2	John Arbash Meinel		14 years ago
46	Add ZLIB to the build process. Add ZLIB to the build process. It seems that on all the test locations, zlib's devel libraries were already in the PATH, so the build routines didn't need to correctly install it themselves. This should fix that.	John Arbash Meinel		14 years ago
45	Hexagonit released a new 1.3.0 version which now is Hexagonit released a new 1.3.0 version which now is only compatible with zc.buildout 1.4.0+. However, we were version locked to zc.buildout 1.2.1. Rather than try to figure out all the things I need to do to use a newer hexagonit, just version lock to the old version.	John Arbash Meinel		14 years ago
44	We no longer bundle tbzr_old.dll since 0.3.1 We no longer bundle tbzr_old.dll since 0.3.1	John Arbash Meinel		14 years ago
43	prepare for the bzr 2.0.2 release. prepare for the bzr 2.0.2 release.	John Arbash Meinel		14 years ago
42	need to update bzrtools and bzr-doc for 2.0.1... argh... need to update bzrtools and bzr-doc for 2.0.1... argh...	John Arbash Meinel	bzr-win32-2.0.1-1	14 years ago
41	subvertpy 0.7.0 fails to build against our current svn libs. subvertpy 0.7.0 fails to build against our current svn libs. I'm assuming 0.7.0 is using something from a newer APR version. For now, just reverting to 0.6.9.	John Arbash Meinel		14 years ago
40	use qbzr 0.14.4 for the 2.0.1 installer. use qbzr 0.14.4 for the 2.0.1 installer.	John Arbash Meinel		14 years ago
39	We also have to export the appropriate TBZR environment vari... We also have to export the appropriate TBZR environment variable. It isn't enough to just run 'python setup.py build' in the right tbzr, we also need to include it in the search path. This seems to be working now.	John Arbash Meinel		14 years ago
38	Depend on new subvertpy. Depend on new subvertpy.	Jelmer Vernooij		14 years ago
37	Change the tortoisebzr build to actually build the named tag... Change the tortoisebzr build to actually build the named tag, rather than always building from 'trunk'.	John Arbash Meinel		14 years ago
36	Work around the bugs in updating by nuking the 'trunk' dirs. Work around the bugs in updating by nuking the 'trunk' dirs. This will make it harder to 'fake' tags, but hopefully I won't have to do that. I wonder if the issue is that the update code is runinng 'bzr update', but these branches aren't checkouts, so it should be running 'bzr pull'... Anyway, the code is currently set up to create shared repositories, so this should allow us to re-use everything we have downloaded, and just have to rebuild the working tree for each project. A bit of a shame, but a small price to pay for updates that actually work.	John Arbash Meinel		14 years ago

Older »