(CC me, I'm not subscribed to debian-devel or maintain ports :D)
Hi,
# norust build profile
I propose we add a `norust` build profile such that packages
building Rust parts or integrating with Rust parts can
disable those parts.
For example, if apt gains sqv support, we can define a
pkg.apt.nosqv buildprofile, but it would be nice to just
use norust too.
The norust profile must NOT be used by packages building
exclusively Rust pieces, that is, it should be possible
to bootstrap a Rust toolchain and package set with the
profile set (and potentially you need externally built
cargo idk).
# setting the profile
I then propose we inject the
DEB_BUILD_PROFILES=norust
in the buildds for the ports architectures that do not have
a rustc.
This would allow them to build packages with optional Rust
parts with reduced functionality. The same can be applied
to other toolchains.
This avoids having to encode entire lists of architectures
for those packages.
## caveats
There is a caveat in that local builds do not know about
the profiles the buildds have set. This means that you
may not easily be able to build packages locally that
are available in the ports archive.
This could be solved by encoding the build profiles in the
dpkg vendor module instead, but it may also be beneficial
to be able to experiment more and have local builds try
to build with everything.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
