Re: pure python and postinst
G'day,
just going through my old inbox messages that didn't seem to be replied
to;
On Mon, 2002-11-18 at 13:11, Steve M. Robbins wrote:
> Howdy,
>
> I've just finished my first attempt at packaging a python module.
> This module (people.debian.org/~smr/pyvtk) is purely python.
>
> I followed the "python policy" outlined in /usr/share/doc/python, and
> also looked at a couple of example packages.
>
> One thing I noticed in the packages (that isn't covered in the policy)
> is the practice of deleting the ".pyc" files in debian/rules, and
> then running "compileall.py" in the postinst. Would someone comment on
> this? Is it a requirement -- is it a bug to include the compiled
> python files in the .deb?
You are not explicitly prevented from including pyc files in your
package, but it is a very bad idea to do so because;
1) it bloats the package with unnecessary files that can be generated at
install time.
2) it ties you package to the particular version of python used to
generate the pyc files (ie, you had better have "Depends: python2.1" if
the .pyc's were generated with python 2.1)
3) it's not the convention... anywhere... even distutils generated rpm's
don't include the pyc files.
--
----------------------------------------------------------------
Donovan Baarda http://minkirri.apana.org.au/~abo/
----------------------------------------------------------------
Reply to: