Re: RE : RE : RE : cctbx debian package
- To: debian-science@lists.debian.org
- Subject: Re: RE : RE : RE : cctbx debian package
- From: Baptiste Carvello <devel@baptiste-carvello.net>
- Date: Mon, 09 Jul 2012 22:33:12 +0200
- Message-id: <[🔎] jtff7f$v9f$1@dough.gmane.org>
- In-reply-to: <[🔎] 20120709105329.GF2610@gmail.com>
- References: <A2A20EC3B8560D408356CAC2FC148E53568D9498@SUN-DAG1.synchrotron-soleil.fr> <20120708215017.GA14150@gmail.com> <A2A20EC3B8560D408356CAC2FC148E53568EBB8A@SUN-DAG1.synchrotron-soleil.fr> <A2A20EC3B8560D408356CAC2FC148E53568EBBA9@SUN-DAG1.synchrotron-soleil.fr> <20120709092321.GA2610@gmail.com> <A2A20EC3B8560D408356CAC2FC148E53568EBD03@SUN-DAG1.synchrotron-soleil.fr> <20120709101240.GB2610@gmail.com> <A2A20EC3B8560D408356CAC2FC148E53568EBDA5@SUN-DAG1.synchrotron-soleil.fr> <[🔎] 20120709105329.GF2610@gmail.com>
Le 09/07/2012 12:53, Radostan Riedel a écrit :
> Baptiste can you tell us your opinion.
>
Hi Radi, hi Frédéric,
I'm still around, but I've been fighting with the tools (cowbuilder
mostly, it now works, and I get the same build error as Frédéric).
Regarding the python packages, I don't think we can rely much on the
upstream build system, as they just set PYTHONPATH and use the modules
in-place in the source tree. So we'll have to copy the .py files, and
maybe a few data files too (not sure, I found some, but they seem to
only be used in tests).
As far as the setup.py is concerned, my proposition would be to write a
fake 'build' stage that executes after the upstream build system and
only copies the files to the appropriate places, so that the distutils
'install' stage can find them.
Cheers,
Baptiste
Reply to: