How about: depending on a targetType "none" package trigger an error?

[p0nce]

It seems to create confusion.

• if I create a parent package that depends on all subpackages, then people think it's a good idea and depend on everything. Remember that NG post with 150 deps?
• if I create a parent package with no dependencies on children, then it also create confusion: https://github.com/p0nce/dplug/issues/108

Maybe a solution would be to warn about the targetType "none" package with a message.

warning: this project depend on a targetType none package. Prefer depending on sub-packages instead.

[veelo]

Depending on a targetType "none" package is useful if it has any preGenerateCommands and/or copyFiles that you want executed for multiple similar packages.

[WebFreak001]

we can still determine which packages are empty without effects (no dependencies, no commands, no copy files) and warn for those.