On Tue, Sep 10, 2013 at 11:34:29PM +0200, Andreas Enge wrote:
Maybe. Bazaar does. Calibre creates elf executables, but also installs
python modules. So I will go ahead with this.
Okay, done in commit 824af8cadc1b4f1ac7a859f3d18cbe69b195a844, and used
for python(2)-setuptools and a new package
Andreas Enge andr...@enge.fr skribis:
On Tue, Sep 10, 2013 at 11:34:29PM +0200, Andreas Enge wrote:
Maybe. Bazaar does. Calibre creates elf executables, but also installs
python modules. So I will go ahead with this.
Okay, done in commit 824af8cadc1b4f1ac7a859f3d18cbe69b195a844, and used
On Tue, Sep 10, 2013 at 10:26:55AM +0200, Andreas Enge wrote:
Maybe we should try to use a variable name %python-standard-phases instead.
The attached patch to guix/build/python-build-system.scm does just this
and works. Would it make sense to push it?
The part of the patch adding
On Tue, Sep 10, 2013 at 07:48:30PM +0200, Ludovic Courtès wrote:
You’re mixing different things: the line above is on the host side,
whereas the patch I proposed changes the modules imported on the build
side.
Okay, I get it!
Can you try this patch to check the value of ‘phases’?
Without
So the next module python-dateutil works. But again,
python setup.py install
complains that the path it wishes to install to,
/nix/store/q637nhgrixha1f8cfl32l6gvviha737g-python2-dateutil-1.5/lib/python2.7/site-packages
does not exist and is not in PYTHONPATH.
So I added the following:
Andreas Enge andr...@enge.fr skribis:
We need to factor this out. I suggest to do the following:
In the install phase, before running setup.py, we create the directory and
add it to the python path. But this would only be needed for programs creating
modules, and I suppose not for programs
Andreas Enge andr...@enge.fr skribis:
So indeed, your patch solves the confusion!
Excellent, thanks!
Ludo’.
Andreas Enge andr...@enge.fr skribis:
On Tue, Sep 10, 2013 at 10:26:55AM +0200, Andreas Enge wrote:
Maybe we should try to use a variable name %python-standard-phases instead.
The attached patch to guix/build/python-build-system.scm does just this
and works. Would it make sense to push it?
Andreas Enge andr...@enge.fr skribis:
On Mon, Sep 09, 2013 at 11:35:55PM +0200, Ludovic Courtès wrote:
The problem is that both the gnu-build-system and the
python-build-system were getting imported, and both export a
‘%standard-phases’.
That is what I thought. I tried to add a
