Hi.
On Mon, Dec 17, 2001 at 08:14:46PM -0600, Joe Reinhardt wrote:
> What is the best way to use the setup.py in the debian/rules?
Added lines marked with "+++"
+++ PYTHON=python2.1
+++ PACKAGE=scipy
> configure: configure-stamp
> configure-stamp:
> dh_testdir
> # Add here commands t
On Mon, Dec 17, 2001 at 06:32:51PM -0800, Neil Schemenauer wrote:
> Joe Reinhardt wrote:
> > -python setup.py bdist
> > cd debian/scipy && tar zxvf ../../dist/SciPy-0.2.0.linux-*.tar.gz
>
> The install command takes a --prefix argument. That might be cleaner
> than using bdist.
I thought
Neil Schemenauer <[EMAIL PROTECTED]> writes:
> Joe Reinhardt wrote:
>> -python setup.py bdist
>> cd debian/scipy && tar zxvf ../../dist/SciPy-0.2.0.linux-*.tar.gz
>
> The install command takes a --prefix argument. That might be cleaner
> than using bdist.
Thanks, this is just what I n
Joe Reinhardt wrote:
> -python setup.py bdist
> cd debian/scipy && tar zxvf ../../dist/SciPy-0.2.0.linux-*.tar.gz
The install command takes a --prefix argument. That might be cleaner
than using bdist.
Neil
Hi,
I just finished packaging scipy (www.scipy.org). Scipy uses a pretty
complicated setup.py file that manages running f2py, compiling f77
code, compiling several helper modules (including a patched copy of
Numeric), etc.
Most of the python modules I have seen packaged for debian use a
makefil
5 matches
Mail list logo