Re: Can/should we have an efi/efi-any platform architecture?
On 12/12/14 10:40, Johannes Schauer wrote:
> Secondly, what you are expressing with:
>
> valgrind-dev <archfeature.valgrind>
>
> is that you do or do not depend on the package valgrind-dev depending on
> whether or not "archfeature.valgrind" evaluates to true (however this is
> resolved).
Yes, but I think that's exactly what I want for dbus' use-case? I want
to build-depend on valgrind (I thought it was valgrind-dev, but it's
actually valgrind) on exactly those architectures to which valgrind has
been ported, so that the debug "flavour" of libdbus can have its
optional valgrind instrumentation on those architectures; but on
architectures to which valgrind has not yet been ported, dbus still
needs to produce working binaries.
Some packages solve this by copying (a random snapshot of) the valgrind
headers into their source code, but I'd prefer to minimize the number of
embedded code copies.
At the moment that's:
Build-Depends: ..., valgrind [amd64 armhf i386 mips mipsel powerpc ppc64
s390x], ...
which is an inconvenient amount of hard-coding, and has led to one RC
bug already (when valgrind dropped support for armel). With build
profiles (which I'll reinstate in unstable when jessie becomes stable)
it would be something like:
Build-Depends: ..., valgrind [amd64 armhf i386 mips mipsel powerpc ppc64
s390x] <!stage1>, ...
but I'd rather have
Build-Depends: ..., valgrind <arch-where-valgrind-exists> <!stage1>, ...
or whatever spelling.
Similarly, db5.3 has
Build-Depends: ..., default-jdk [!m68k], ...
(and other Java things on [!m68k])
and gdcm has
Build-Depends: ..., cli-common-dev (>= 0.8~) [amd64 armel i386
kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x], ...
(and other Mono things on those architectures)
but there'd be no need for the Java and Mono maintainers to coordinate
these ad-hoc architecture lists with other maintainers via bugs like
#719842, #575138, #541612, #477855, #699379, #657779 if packages like
db5.3 and gdcm could instead say:
Build-Depends: ..., default-jdk <arch-where-java-exists>, ...
Build-Depends: ..., cli-common-dev <arch-where-mono-exists>, ...
Regards,
S
Reply to: