Am I right in assumption that you arguing about *_TARGETS rework to be enabled by default for packages that was not tested on this TARGETs with ... hardness of packaging java software?..
Or does it just argmentum ad verecundiam (with argumentum ad hominem partially)? And yes, I personally packaged Java software from scratch (including all the depends). And yes, some times I even thought "F**k this sh*t!" (but finished packaging afterwards). And yes, I packaged Go software. And yes, I packaged NodeJS software. And no, they are NOT much easy to package then Java one (even including they still have no TARGETS... As java? :D). But how does it apply to TARGETS logic breakage? The purpose of TARGETS is that package holds only that TARGETs that it was tested to work against. It is wrong to have any targets enabled by default for all the packages and removing in case if it is broken. Instead, if new target appeared a month (year, decade) ago, but package, that you're interested in, still doesn't support it... Well.. It meant, maintainer is a slacker and package is a candidate to last-rites and removal...
