Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #13120

Re: Generic Python packages which don’t work on all architectures

From Paul Wise <pabs@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Generic Python packages which don’t work on all architectures
Date 2021-01-21 02:50 +0100
Message-ID <BzxgJ-6DT-1@gated-at.bofh.it> (permalink)
References <BzrEm-35B-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Jan 20, 2021 at 7:40 PM Stephen Kitt wrote:

> I’ve come across a situation which doesn’t seem to be addressed by existing
> policies: the python-ptrace source package only ships
> architecture-independent content, but it works on a small number of
> architectures (currently, 32/64-bit x86, 32-bit ARM, 32/64-bit PPC).

The iotop package is in a similar situation, it uses Linux kernel APIs
so does not work on Hurd or kFreeBSD.

> As a result, the packages it builds are installable everywhere, but that’s a
> false promise since they don’t work everywhere. Would it make sense to
> convert it to an architecture-dependent package, only on those architectures
> which are really supported?

This is what I eventually chose for iotop. At the time I wanted dpkg
and dak to support something like Architecture: linux-all, which would
build arch: all packages, but only put them in the Packages files for
the Linux architectures.

I am now thinking that a more generic solution than Architecture:
linux-all is needed, in order to cover your case as well. Perhaps
something like Available-Architecures or Runtime-Architectures or
Architecture-all-Architectures: or similar.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Generic Python packages which don’t work on all  architectures Stephen Kitt <skitt@debian.org> - 2021-01-20 20:50 +0100
  Re: Generic Python packages which don’t work on all architectures Matthias Klose <doko@debian.org> - 2021-01-20 21:10 +0100
  Re: Generic Python packages which don’t work on all architectures Paul Wise <pabs@debian.org> - 2021-01-21 02:50 +0100
    Re: Generic Python packages which don’t work on all architectures Christian Kastner <ckk@debian.org> - 2021-01-21 08:10 +0100
    Re: Generic Python packages which don’t work on all architectures Ole Streicher <olebole@debian.org> - 2021-01-21 14:20 +0100
      Re: Generic Python packages which don’t work on all architectures Paul Wise <pabs@debian.org> - 2021-01-21 14:30 +0100
        Re: Generic Python packages which don’t work on all architectures Ole Streicher <olebole@debian.org> - 2021-01-21 16:50 +0100
          Re: Generic Python packages which don’t work on all architectures Paul Wise <pabs@debian.org> - 2021-01-22 00:40 +0100
            Re: Generic Python packages which don’t work on all architectures Paul Wise <pabs@debian.org> - 2021-01-22 00:50 +0100
            Re: Generic Python packages which don’t work on all architectures Ole Streicher <olebole@debian.org> - 2021-01-22 10:00 +0100
      Re: Generic Python packages which don’t work on  all architectures Ansgar <ansgar@43-1.org> - 2021-01-21 14:40 +0100
        Re: Generic Python packages which don’t work on all architectures Ole Streicher <olebole@debian.org> - 2021-01-21 16:20 +0100

csiph-web