zc.buildout-1.7.0b2 released
The main goal of the 1.7 release is to provide an update for buildout 1 that won't upgrade itself to buildout 2. zc.buildout-1.7.0b2 fixes a backward-compatibility problem reported in zc.buildout-1.7.0b1. To get the release, download the new buildout 1 bootstrap.py script from http://downloads.buildout.org/1/bootstrap.py: wget http://downloads.buildout.org/1/bootstrap.py and use it to bootstrap your projects. Because this is a non-final release, you need to use the -t option when you run it: python bootstrap.py -t Please try it and let me know if you have any problems. If I don't hear anything, I'll release 1.7.0 final in a week or so. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
Jim Fulton
Please try it and let me know if you have any problems. If I don't hear anything, I'll release 1.7.0 final in a week or so.
I tried upgrading one of my projects to 1.7.0b2 (from 1.6.0), and something has changed wrt the location where the buildout script is written. I usually keep all buildout related stuff, including its configuration files, in a ``buildout`` subdirectory of the project's top level, such as:: . ├── bin/ ├── buildout/ │ ├── buildout.cfg │ ├── versions.cfg │ └── ... ├── src/ │ └── ... The top level ``Makefile`` takes care of bootstrapping and executing the buildout, with something like the following targets: export TOPDIR := $(CURDIR) BINDIR := $(TOPDIR)/bin .PHONY: all all: buildout BUILDOUT := $(BINDIR)/buildout BODIR := $(TOPDIR)/buildout BOCFGS := $(wildcard $(BODIR)/*.cfg) BOTSTAMP := $(BODIR)/timestamp BOMAIN := $(BODIR)/buildout.cfg BOCACHE := $(HOME)/.buildout/dlcache BOPARTS := $(BODIR)/parts BOSTATUS := $(BODIR)/status BOFLAGS := -c $(BOMAIN) \ buildout:directory=$(TOPDIR) \ buildout:parts-directory=$(BOPARTS) \ buildout:download-cache=$(BOCACHE) \ buildout:installed=$(BOSTATUS) .PHONY: buildout buildout: $(BUILDOUT) $(BOTSTAMP) $(BUILDOUT): bootstrap.py mkdir -p $(BOCACHE) python bootstrap.py -t $(BOFLAGS) $(BOTSTAMP): $(BOCFGS) $(BUILDOUT) $(BOFLAGS) @touch $(BOTSTAMP) clean: rm -f $(BOTSTAMP) realclean: clean rm -f $(BOSTATUS) distclean: realclean rm -rf $(BOPARTS) $(BINDIR) develop-eggs Up to buildout version 1.6.0 this used to create a ``bin/buildout`` script under the top level directory (the ``buildout:directory`` option is pointing to that directory). This is not the case anymore: I tried with both 1.7.0b2 and with 2.0.0a5, and the ``buildout`` script is created inconditionally *below* the ``buildout`` directory, that is ``buildout/bin/buildout``. It seems a regression to me, but maybe I missing some other option that controls the location... thanks in advance for any hint, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
Lele Gaifax
I tried upgrading one of my projects to 1.7.0b2 (from 1.6.0), and something has changed wrt the location where the buildout script is written.
The "regression" was introduced by 88eb20328fc0fcdec3a7fa555393573e632315a8 when the logic at the end of the bootstrap.py was changed "to correctly handle bootstrap and init commands". FYI, since I noticed latest commit by Jim on the master branch (f946e1fccb37978a1667505ee2822c19fd6effcc), applying a similar change to the 1.7.0b2 bootstrap.py fixed the problem. thanks&bye, lele -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
On Fri, Jan 4, 2013 at 9:44 AM, Lele Gaifax
Jim Fulton
writes: Please try it and let me know if you have any problems. If I don't hear anything, I'll release 1.7.0 final in a week or so.
I tried upgrading one of my projects to 1.7.0b2 (from 1.6.0), and something has changed wrt the location where the buildout script is written.
I usually keep all buildout related stuff, including its configuration files, in a ``buildout`` subdirectory of the project's top level, such as::
. ├── bin/ ├── buildout/ │ ├── buildout.cfg │ ├── versions.cfg │ └── ... ├── src/ │ └── ...
The top level ``Makefile`` takes care of bootstrapping and executing the buildout, with something like the following targets:
export TOPDIR := $(CURDIR) BINDIR := $(TOPDIR)/bin
.PHONY: all all: buildout
BUILDOUT := $(BINDIR)/buildout BODIR := $(TOPDIR)/buildout BOCFGS := $(wildcard $(BODIR)/*.cfg) BOTSTAMP := $(BODIR)/timestamp BOMAIN := $(BODIR)/buildout.cfg BOCACHE := $(HOME)/.buildout/dlcache BOPARTS := $(BODIR)/parts BOSTATUS := $(BODIR)/status BOFLAGS := -c $(BOMAIN) \ buildout:directory=$(TOPDIR) \ buildout:parts-directory=$(BOPARTS) \ buildout:download-cache=$(BOCACHE) \ buildout:installed=$(BOSTATUS)
.PHONY: buildout buildout: $(BUILDOUT) $(BOTSTAMP)
$(BUILDOUT): bootstrap.py mkdir -p $(BOCACHE) python bootstrap.py -t $(BOFLAGS)
$(BOTSTAMP): $(BOCFGS) $(BUILDOUT) $(BOFLAGS) @touch $(BOTSTAMP)
clean: rm -f $(BOTSTAMP)
realclean: clean rm -f $(BOSTATUS)
distclean: realclean rm -rf $(BOPARTS) $(BINDIR) develop-eggs
You know, one of the reasons I wrote buildout was so I wouldn't have to look at Makefiles.
Up to buildout version 1.6.0 this used to create a ``bin/buildout`` script under the top level directory (the ``buildout:directory`` option is pointing to that directory).
This is not the case anymore: I tried with both 1.7.0b2 and with 2.0.0a5, and the ``buildout`` script is created inconditionally *below* the ``buildout`` directory, that is ``buildout/bin/buildout``.
It seems a regression to me, but maybe I missing some other option that controls the location...
I've uploaded a new buildout 1 bootstrap script: http://downloads.buildout.org/1/bootstrap.py It should fix the problem you're having with buildout 1.7. I'll release a new buildout 2 bootstrap script when I release buildout 2.0.0a6. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
Jim Fulton
You know, one of the reasons I wrote buildout was so I wouldn't have to look at Makefiles.
I can imagine, but if you're luck enough to work only on serious OSes, taking advantage of "make" being both shorter to type and way faster to decide whether there is actually anything that needs to be built... well, you surely can tolerate the hassle :-)
I've uploaded a new buildout 1 bootstrap script:
http://downloads.buildout.org/1/bootstrap.py
It should fix the problem you're having with buildout 1.7.
I'll release a new buildout 2 bootstrap script when I release buildout 2.0.0a6.
Great, thank you! bye, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
Jim Fulton
Please try it and let me know if you have any problems. If I don't hear anything, I'll release 1.7.0 final in a week or so.
I notice a little typo in the CHANGES.txt, where there is a duplicated entry for 1.7.0b1, instead of a new 1.7.0b2. ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
On Fri, Jan 4, 2013 at 10:33 AM, Lele Gaifax
Jim Fulton
writes: Please try it and let me know if you have any problems. If I don't hear anything, I'll release 1.7.0 final in a week or so.
I notice a little typo in the CHANGES.txt, where there is a duplicated entry for 1.7.0b1, instead of a new 1.7.0b2.
Oops. Thanks. Fix committed. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
participants (2)
-
Jim Fulton
-
Lele Gaifax