On Thu, Oct 24, 2024 at 01:29:31AM +0200, Ben Hutchings wrote:
> On Sat, 2024-10-19 at 15:35 +0200, Bastian Blank wrote:
> > I have to disagree. With this setup, we can support architectures that
> > are neither known by dpkg nor dak. This was not possible before and
> > required patching, aka making a derivative of the package. You can
> > still patch and rebuild it how you want and inject that modified package
> > into your workflow.
> Currently gencontrol.py runs dpkg-architecture to find the multiarch
> triplet for each Debian architecture. So it's not possible to add any
> architecture that's unknown to dpkg in unstable.
> Are you proposing to extend our config schema so we can define those
> triplets within src:linux?
I did add that support first.
> Do we really want to be on the critical path for the early stages of
> defining a new architecture, including any renaming that might happen
> before it's added to dpkg upstream?
Which early stages? We have three stages:
- Before the arch reaches anything related to Debian. In this stage, it
does not matter if the package it all or any, it can be patched.
- While it lives on -ports, but dak does not know about it. In this
stage, the package needs to be managed manually.
- While it lived on -ports and dak knows about. In this stage, support
can be added as arch:any.
Bastian
--
... The prejudices people feel about each other disappear when they get
to know each other.
-- Kirk, "Elaan of Troyius", stardate 4372.5
