Hi,
If I have the choice, I would go for the second solution. So tell the
system to build on all architectures and remove the runtime dependency
to chromium on s390x armel and mips64el . I think mediawiki2latex can
still be used in a practical way even if chromium is not available. For
many years mediawiki2latex was used without any option to use chromium
any way. I am not sure if Georges knows the syntax to add such an
architecture qualified depends on chromium. I didn't find any out in a
quick internet search. So could you Paul please post some information on
how to do that. Maybe an example.
Yours Dirk
On 15.02.24 15:33, Paul Gevers wrote:
Hi,
On 15-02-2024 08:40, Dirk Hünniger wrote:
So it still wants to build on s390x armel and mips64el. Possibly its
not possible to drop support for an architecture that once was
supported.
This is not the solution *I* had in mind. I was thinking about just
adding an architecture qualified depends on chromium, not only build
on the non-chromium architectures. If you want to continue the current
route, instead of hardcoding the architectures, I would add a
*build*-depends on chromium to prevent building on architectures where
it's not available. Then the package automatically builds on those
once chromium becomes available.
Once an architecture builds successfully, it requires actions from
ftp-master to remove the binaries. So, $(reportbug ftp.debian.org) if
the architectures are fully unsupported.
So possible we need to tell the system that it can still build on all
architectures, but the the dependency to chromium is only needed on
all architectures but s390x armel and mips64el
That's what I had in mind indeed.
Paul
