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

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

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

Show all headers | View raw

Ansgar <ansgar@43-1.org> writes:
> On Thu, 2021-01-21 at 13:46 +0100, Ole Streicher wrote:
>> I am still wondering why we don't have just empty some pseudo-
> packages that are available only on specific architectures
>> (or  groups of them, like linux, or little endian, or 64 bit or so).
>
> To solve which problem?

For example, the problem that a certain package is working properly only
on big endian systems. Or on Linux.

Currently, there is (as discussed here) no way to tell that an arch:all
package is not working on a 32-bit system. And for architecture
dependent builds, one needs to specify every single architecture where
it is supposed to build. How do you currently otherwise would specify
"all little endian systems" as build dependency?

> Packages being installable don't mean that they can do anything useful
> as they might, for example, require special hardware.  We don't have a
> way to express "requires device ${X}" on a package level.

Special hardware is another topic, which is surely not solved here (and
not solvable at all in general, since hardware today may be
hot-pluggable, and the hardware configuration at install time does not
need to be the configuration at run time).

However, the proposal to have architecture (group) specific empty
packages would already solve some of the problems if this is limited to
architecture specification.

Best regards

Ole

Back to linux.debian.maint.python | Previous | Next — Previous 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