I have some notes for the current blends-dev implementation:
As I saw in the blends/devtools/Makefile the produced debian/control file is built as following:
* first it contains the content of the debian/control.stub. this file contains the blend info along with extra fields such as Build-Depends-Indep, priority etc (the UDD blends_metadata contains most of these data, also the UDD sources)
I assume my script will get the blend-name for the control.stub file (like the current blend-gen-control does)
* then the Makefile checks if a config/control file exists, if yes it also "appends" its content in the debian/control file
* finally the blend-gen-control is called and "appends" the tasks info in the final debian/control.
I assume that the first two steps are going to be the same? Then the new blend-gen-control will dump in the stdout (or append in an existing file) the task info (the rest will be taken from the control.stub and config/control). I also assume the new blend-gen-control should will the -D argument(lower all Depends: to Recommends:).
Also I observed that the "Avoid" packages are not saved in the UDD blends_dependencies(thus we can not have the excluded list as the curreny blends-dev has). For the moment blends-gen-control will keep a list of the "missing packages" while creating the blends_dependecies dictionary needed for gen_control method.