>> In my view, it is the responsibility of the people writing the tasks
>> to decide if a package in contrib should use recommends or suggest,
>> not the blends build system.
> No. Recommends need to reside in main (per policy).
I believe I understand what both you and Ola mean, and your description
matches my understanding of how blends-dev work. It does not match how
I understand Ole. If someone create a task with contrib and non-free in
the associated sources.list, any packages in contrib and non-free will
be detected as present and allowed to be listed as recommends. If the
sources.list file do not list contrib and non-free, as any policy
compliant task setup should, then no package from contrib and non-free
will be listed as recommended in the resulting task package.
I understand Ole to claim that blends-dev previously would somehow
filter packages from contrib and non-free even if they are listed as
present using the sources.list entries. This do not match my
understanding of how blends-dev ever worked.
I believe that if someone need or want to create a unofficial task with
some packages in contrib, non-free or some unofficial APT source, they
should be allowed to do so by listing these entries in their
sources.list files. And those of us uploading tasks to debian/main
should not list anything byt debian/main in our sources.list files.