Hi, On 4/3/26 4:47 PM, Paul Gevers wrote:
On 4/2/26 22:27, Michael Tokarev wrote:
Besides backports, this same mechanism can be implemented in context of distribution. For example, distribution.ubuntu build profile vs distribution.debian, etc - it will help greatly to distinguish the [build] dependencies for example, as ubuntu has universe vs main.
The wiki has a rationale why doing that is not a great idea [1]. [1] https://wiki.debian.org/BuildProfileSpec#Derivative_specific_profiles
Yeah, also I believe that is already largely covered with vendor profiles -- although these have the disadvantage that we can't use them in Build-Depends.
If you plan to pursue this endeavor, please be aware that there is tooling out that that currently relies on the fact that the official Debian buildds do not use/allow build profiles.
This would only be relevant for backports. I agree that it makes sense for unstable and testing not to use any build profiles -- but
Build-Depends: qtbase5-dev <bookworm>, libqt5opengl5-desktop-dev <bookworm>, qt6-base-dev <!bookworm> is just *very* convenient for a backport. Simon
