d.w.morriss at gmail.com
Tue Nov 21 17:47:36 EET 2006
Kai Lautaportti wrote:
> Hi whit
> Thanks for the feedback. I haven't tried running the buildout in
> workingenv myself but this is something we can and should definitely
> look into.
> The initial reason for me to put together the buildout was to provide an
> all-or-nothing solution for getting all the components installed. Now
> that this seems to be working we can move onto making the buildout
> support partial installation better where you can optionally use system
> installed components as part of the installation.
> I'd be happy to hear from anyone on how to do this in the most
> easy-to-use way and also which components of the buildout would most
> likely need to support partial installation.
> whit wrote:
>> just some quick feedback. tried running the prima.buildout in a
>> workingenv python environment and ran into a couple things.
>> * downloads and installs a new python. is there a flag I can tick to
>> avoid this?
> Currently there is no flag to do this. However, all the tasks that
> depend on python simply assume that the interpreter is located under
> $PREFIX/bin/python2.4. If you provide a symlink at the given location
> pointing to your existing python interpreter and simply comment out the
> python task in build.py, you might be able to use your own python.
> Haven't really tested this though.
easy enough to fix that.
>> * dies looking for PIL in the wrong place w/ a warning about strict targets.
> If you already have PIL somewhere where your own python interpreter is
> able to find it, you can most likely just comment the PIL task out from
> build.py or alternatively modify the "targets" parameter in the
> "install" task within $BUILDOUT/tasks/pil.py to point to your existing
> PIL installation which will then satisfy the strict target check.
cool! will do!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 291 bytes
Desc: not available
More information about the Community