Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8407
| From | Paul Wise <pabs@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Cythonized files & Debian Policy |
| Date | 2016-04-08 05:40 +0200 |
| Message-ID | <rlvr3-64m-3@gated-at.bofh.it> (permalink) |
| References | <rlpF0-1zn-5@gated-at.bofh.it> <rlr45-2w5-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Apr 8, 2016 at 6:42 AM, Scott Kitterman wrote: > The only way to reliably know if it can be built is to do so as part of the package build, so you should regenerate the binary file and install that in your package. In addition, removing the generated files in `debian/rules clean` and `debian/rules build` (before any of the upstream configure/build stuff runs) is a good idea to make sure that the existing generated files do not leak into the build process. -- bye, pabs https://wiki.debian.org/PaulWise
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Cythonized files & Debian Policy Víctor Cuadrado Juan <me@viccuad.me> - 2016-04-07 23:30 +0200
Re: Cythonized files & Debian Policy Scott Kitterman <debian@kitterman.com> - 2016-04-08 01:00 +0200
Re: Cythonized files & Debian Policy Paul Wise <pabs@debian.org> - 2016-04-08 05:40 +0200
csiph-web