Path: csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!news.uzoreto.com!aioe.org!bofh.it!news.nic.it!robomod From: Ole Streicher Newsgroups: linux.debian.maint.python Subject: Re: Generic Python packages which =?utf-8?Q?don=E2=80=99t?= work on all architectures Date: Thu, 21 Jan 2021 14:20:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Jan 21 13:12:12 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.464 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.249, KHOP_HELO_FCRDNS=0.399, LDO_WHITELIST=-5, SARE_HEAD_8BIT_SPAM=0.888] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -5.5 X-Greylist: delayed 522 seconds by postgrey-1.36 at bendel; Thu, 21 Jan 2021 12:55:25 UTC User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Lines: 23 X-Mailing-List: archive/latest/18899 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87zh12ihk6.fsf@burgos Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 21 Jan 2021 13:46:17 +0100 X-Original-Message-ID: <87zh12ihk6.fsf@burgos> X-Original-References: <20210120203941.1a41cc06@heffalump.sk2.org> Xref: csiph.com linux.debian.maint.python:13123 Paul Wise writes: > 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. 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). If a package works (or builds) only on a specific arch (or an arch with specific properties), it can be set dependent (or built-dependent) on that. This would be a quite flexible and extendible approach to have packages installable only where they work. Best regards Ole