* Giulio Paci <giuliop...@gmail.com>, 2013-04-06, 04:37:
http://lists.debian.org/20130216120158.ga3...@jwilk.net
Okay. So I see the following ways to go forward:
B) Install the modules as public ones, but put them in a namespace
starting with underscore, say _sequitur_gp2.
C1) Build the modules only for the default Python version and install
them to a private directory (/usr/lib/sequitur-gp2/). But then this
will trigger #702677, so either implement a work-around for it, or
wait until it's fixed, or switch back to python-support...
I leave to your discretion which option to choose. B is my preference,
although it didn't gain recognition on debian-python.
Switched back to python-support and implemented C1.
"python-dev (>= 2.6.6-9)" - why this version?
There are some tests, it would be good to run them at build time.
(Although at least some of them seem to only touch code that doesn't
even end up in binary packages...)
Enabled the relevant tests.
Do you honour DEB_BUILD_OPTIONS=nocheck? :)
Did you manually edit the manpage?
otherwise it might be a good idea to regenerate it at build time.
Now it is generated at build time.
Great.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130407200029.ga5...@jwilk.net
