On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
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
On Wed, Nov 20, 2002 at 10:12:31AM +, Julian Gilbey wrote:
On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
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
On Tue, Nov 19, 2002 at 09:06:55PM -0600, Graham Wilson wrote:
they are not included because that would just be extra space taken up in
the .deb file for something which can be generated on the users machine.
No, that is the point of a .deb, to pre-generate and pre-install things for
the user.
On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
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
On Wed, Nov 20, 2002 at 10:12:31AM +, Julian Gilbey wrote:
On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
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
On Tue, Nov 19, 2002 at 09:06:55PM -0600, Graham Wilson wrote:
they are not included because that would just be extra space taken up in
the .deb file for something which can be generated on the users machine.
No, that is the point of a .deb, to pre-generate and pre-install things for
the user.
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
On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
Howdy,
hello.
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?
On Tue, Nov 19, 2002 at 09:06:55PM -0600, Graham Wilson wrote:
On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
Howdy,
hello.
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
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
On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
Howdy,
hello.
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?
On Tue, Nov 19, 2002 at 09:06:55PM -0600, Graham Wilson wrote:
On Tue, Nov 19, 2002 at 08:17:28PM -0500, Steve M. Robbins wrote:
Howdy,
hello.
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
12 matches
Mail list logo
