[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 <edd@debian.org> 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



Reply to: