SPECS: python-xmlrpc.spec - I can be python-aware: arch-independen...

Radoslaw Zielinski radek42 at gmail.com
Wed Jul 6 13:53:25 CEST 2005


Paweł Sakowski <saq at pld-linux.org> [05-07-2005 23:21]:
> On Tue, 2005-07-05 at 22:55 +0200, Radosław Zieliński wrote:
>>> Author: saq                          Date: Tue Jul  5 19:18:51 2005 GMT
>>> Module: SPECS                         Tag: HEAD
>>> ---- Log message:
>>> - I can be python-aware: arch-independent dir, minor fixes
>> No, you can't.  If it's supposed to be arch-independent, the package
>> should be noarch
> If all files are arch-independent, yes: the package can be noarch (it's
> a secondary improvement, though). Even if not explicitly marked as such,
> it can still conform with FHS.

>> and *.py{c,o} shouldn't differ between archs.  They do.
> They don't.

The one I've checked before writing that mail did (python-ipaddr). ;-]

> The same version of python produces identical *.py[co] on
> every supported architecture (given the same *.py), give or take the
> timestamp field. A py[co] compiled on any architecture will work fine on
> any other.

I was sure, that *.py[co] are arch-dependent.

I've tested 14 packages for differences between i686 and alpha:

  $ rpm -qp python-* | sort | uniq | xargs | fmt
  python-adns-1.0.0-3 python-biggles-1.6.4-2 python-CDDB-1.4-3
  python-chm-0.8.2-1 python-Crypto-2.0-4 python-EditObj-0.5.6-1
  python-egenix-mx-base-2.0.5-9 python-egenix-mx-experimental-0.7.0-4
  python-epiphany-0.1.4-1 python-eyeD3-0.6.3-1 python-fam-1.0.2-2
  python-gnome-2.10.0-2 python-gstreamer-0.8.1-2 python-ipaddr-1.1-5

  $ diff -r i686 alpha | awk '{print $2}'
  i686/usr/lib/python2.4/site-packages/gtk-2.0/gnome/__init__.pyc
  i686/usr/lib/python2.4/site-packages/gtk-2.0/gnome/__init__.pyo
  i686/usr/lib/python2.4/site-packages/ipaddr.pyc
  i686/usr/lib/python2.4/site-packages/ipaddr.pyo
  i686/usr/share/python2.4/site-packages/eyeD3/__init__.pyc
  i686/usr/share/python2.4/site-packages/eyeD3/__init__.pyo
  i686/usr/share/python2.4/site-packages/gst/__init__.pyc
  i686/usr/share/python2.4/site-packages/gst/__init__.pyo

So, usually, they don't differ, but not always.  Question: do we allow
noarch packages, containing files, which differ between architectures?
IIRC: no, but I may be wrong.

-- 
Radosław Zieliński <radek at pld-linux.org>



More information about the pld-devel-en mailing list