Re: (Ab)using build profiles
On Sun, Nov 02, 2025 at 07:12:52PM +0100, Jérémy Lal wrote:
> To help tracking lots of dependencies in package.json, with how
> debian/control
> dependencies are decided, I've started using build profiles to add some
> inline
> metadata.
>
> Bad idea ? Good idea ?
A few weeks ago I tried building all packages using the nodoc build profile
and found more than 900 packages which failed to build.
This was a little bit disappointing because I expected a lot less.
If/when a package uses <!nodoc> in d/control, we might reasonably assume
that the package wants to support the "nodoc" build profile.
The problem is that a lot of packages do not use <!nodoc> at all
and they FTBFS when using the nodoc build profile. Should we assume
that not using <!nodoc> at all means nodoc is not supported?
Or maybe we need a new field in d/control to declare the supported build profiles?
In this case, using a build profile syntax in d/control when it does
not even match a real build profile which we want to support as a
build profile could amplify the above problem.
So, I would ask in -devel about this.
Thanks.
Reply to: