On Sat, 09 Jul 2016 23:56:03 +0200 Johannes Schauer <jo...@debian.org> wrote: > I'm CC-ing debian-dpkg@.
I cannot CC lists.debian.org. You will not see my messages in https://lists.debian.org/debian-policy/2016/07/threads.html . > I suspect you want to express "this package has to be built when no > profiles are active as well as when the pkg.linux.zlib profile is > active"? Yes. > If so, then why do you need the Build-Profiles field at all? Because the package should not be built if other pkg.linux.* profiles are active. > What is your use case? There is an introduction at https://bugs.debian.org/830524 . The goal is to build a subset of binary packages. For instance, the linux source package should have a way to build only linux-image-4.6.0-1-686 (profile pkg.linux.686), only linux-image-4.6.0-1-rt-686-pae (profile pkg.linux.rt-686-pae), etc. The nodebug profile would be useful to not build *-dbg packages. > > I gather that the Built-For-Profiles field is written to > > DEBIAN/control > Why do you want to avoid this field? Why would this be useful? Binary packages should be exactly the same as if built without active profiles. This helps making and checking a subset of reproducible packages.
smime.p7s
Description: S/MIME cryptographic signature
