Re: Installed wajig 0.2.11-1 (i386 source)
On Sat, Jan 12, 2002 at 01:32:06AM +0900, Junichi Uekawa wrote: > I don't care what FUD is, but apparently I still don't know the > answer to my initial question. > > How should python scripts be packaged ? Unless something else in the package is architecture dependent, the package should be Architecture: all Currently .py and .pyc files should be shipped together in the .deb
Re: Installed wajig 0.2.11-1 (i386 source)
Steve Kowalik <[EMAIL PROTECTED]> cum veritate scripsit:
> > That's a bug in python2.{1,2} then. What's the point of having a platform
> > neutral 'compiled' version of a script if the format changes every time the
> > wind changes direction?
> FUD. Pure FUD.
I don't care what FUD is, but apparently I still don't know the
answer to my initial question.
How should python scripts be packaged ?
regards,
junichi
--
[EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Re: Installed wajig 0.2.11-1 (i386 source)
At 11:17 am, Friday, January 11 2002, Adam Heath mumbled:
> That's a bug in python2.{1,2} then. What's the point of having a platform
> neutral 'compiled' version of a script if the format changes every time the
> wind changes direction?
>
FUD. Pure FUD.
--
Steve
We are Debian of Borg. Resistance is futile! You will be packaged!!
pgpmjFffAg3eq.pgp
Description: PGP signature
Re: Installed wajig 0.2.11-1 (i386 source)
On Thu, 10 Jan 2002, Malcolm Parsons wrote:
> There is no point byte compiling during package creation, as every time
> the python2.{1,2} packages are upgraded, every .py file is byte
> compiled again anyway:
>
> python2.2.postinst:
> for i in $DIRLIST ; do
> /usr/bin/python2.2 -O /usr/lib/python2.2/compileall.py -q $i
> /usr/bin/python2.2 /usr/lib/python2.2/compileall.py -q $i
> done
That's a bug in python2.{1,2} then. What's the point of having a platform
neutral 'compiled' version of a script if the format changes every time the
wind changes direction?
> It's also a waste of archive space, bandwidth, etc.
Make it separate debs then. Also, look at how java is done. The source files
are not shipped.
> As I upgrade over a modem, making packages the useful part of a package 4
> times smaller is IMHO a very good idea.
This should be done right, which means compiling at package build time.
Re: Installed wajig 0.2.11-1 (i386 source)
On Wed, Jan 09, 2002 at 09:07:06PM -0600, Adam Heath wrote:
> On Wed, 9 Jan 2002, Malcolm Parsons wrote:
>
> > python modules should be supplied as source, and byte compiled in the
> > postinst.
>
> No, they should be byte compiled during package creation.
There is no point byte compiling during package creation, as every time
the python2.{1,2} packages are upgraded, every .py file is byte
compiled again anyway:
python2.2.postinst:
for i in $DIRLIST ; do
/usr/bin/python2.2 -O /usr/lib/python2.2/compileall.py -q $i
/usr/bin/python2.2 /usr/lib/python2.2/compileall.py -q $i
done
resulting in:
[EMAIL PROTECTED]:/usr/lib/python2.2/site-packages/Guppi$ ls -l
total 328
-rw-r--r--1 root root71237 Jan 4 21:50 __init__.py
-rw-r--r--1 root root 120672 Jan 9 21:00 __init__.pyc
-rw-r--r--1 root root 115395 Jan 9 21:00 __init__.pyo
Unless you think it took 5 days to build this package?
It's also a waste of archive space, bandwidth, etc.
As I upgrade over a modem, making packages the useful part of a package 4 times
smaller is IMHO a very good idea.
Re: Installed wajig 0.2.11-1 (i386 source)
On Wed, 9 Jan 2002, Malcolm Parsons wrote: > python modules should be supplied as source, and byte compiled in the > postinst. No, they should be byte compiled during package creation.
Re: Installed wajig 0.2.11-1 (i386 source)
On Wed, Jan 09, 2002 at 07:01:15AM -0600, Dirk Eddelbuettel wrote: > On Wed, Jan 09, 2002 at 03:06:52PM +0900, Junichi Uekawa wrote: > > Is byte-compiled python script platform-dependent? > > Is that not correct? Or does an i386 .pyc/.pyo work on other architectures? .pyc and .pyo files are completely portable. At work we use the same .pyc files on solaris, hpux and nt. So I don't see why python files are in /usr/lib, not /usr/share. python modules should be supplied as source, and byte compiled in the postinst.
Re: Installed wajig 0.2.11-1 (i386 source)
Dirk Eddelbuettel <[EMAIL PROTECTED]> cum veritate scripsit: > > Is byte-compiled python script platform-dependent? > > It is my (naive) understanding that it is not. > > Is that not correct? Or does an i386 .pyc/.pyo work on other architectures? I am not quite sure. I also wondered if it was customary to have byte-compiled python scripts. regards, junichi -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Re: Installed wajig 0.2.11-1 (i386 source)
On Wed, Jan 09, 2002 at 03:06:52PM +0900, Junichi Uekawa wrote: > On Tue, 08 Jan 2002 15:13:08 -0500 > Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote: > > > Description: > > wajig - Simplified Debian package management front end > > Changes: > > wajig (0.2.11-1) unstable; urgency=low > > . > >* Upgraded to new upstream release > > Files: > > e2a0aaa255f1fd9404ccc176c82969c2 619 admin optional wajig_0.2.11-1.dsc > > 33e519867e30638235b9611f5dc51d0c 37539 admin optional > > wajig_0.2.11.orig.tar.gz > > b96f5f99b6df7a748a2b53cb16cd67b5 2459 admin optional wajig_0.2.11-1.diff.gz > > I just wondered: > What part of this python script makes it requisite to be > built for each architecture ? > Why isn't it "all" instead of "any"? > > Is byte-compiled python script platform-dependent? It is my (naive) understanding that it is not. Is that not correct? Or does an i386 .pyc/.pyo work on other architectures? Dirk -- Good judgment comes from experience; experience comes from bad judgment. -- F. Brooks
Re: Installed wajig 0.2.11-1 (i386 source)
On Tue, 08 Jan 2002 15:13:08 -0500 Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote: > Description: > wajig - Simplified Debian package management front end > Changes: > wajig (0.2.11-1) unstable; urgency=low > . >* Upgraded to new upstream release > Files: > e2a0aaa255f1fd9404ccc176c82969c2 619 admin optional wajig_0.2.11-1.dsc > 33e519867e30638235b9611f5dc51d0c 37539 admin optional > wajig_0.2.11.orig.tar.gz > b96f5f99b6df7a748a2b53cb16cd67b5 2459 admin optional wajig_0.2.11-1.diff.gz I just wondered: What part of this python script makes it requisite to be built for each architecture ? Why isn't it "all" instead of "any"? Is byte-compiled python script platform-dependent? regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
