I'm not really in favor of these kinds of arguments. It opens a an endless permutations for every package that can deal with every image format. We've always followed the practice that if you enable something in fletch support for it is added. Is there a good reason to force disable? If so, there needs to be a better approach (better engineering) in place that doesn't involve adding these flags for every package. This type of thing requires a larger discussion.

People were reporting build issues in VIAME because of this on a few linux platforms, leaving it turned off resolved said issues, because tiff support in opencv is un-needed in VIAME

You're welcome to merge this branch into viame/master if that helps. If you could provide details about the error we might be able to resolve it. I haven't seen any issues thus far.

It has been, for some time, and viame/master will continue to exist if this isn't merged into master, which is fine by me, but otherwise we could have pegged it to master.

The errors themselves were primarily linking errors on Ubuntu / Fedora, didn't have time to deal with at the time and still don't, it was better for us to just leave it disabled since it's un-needed

Link errors from viame/master or master? There are a lot of fixes in master which relate to this problem.

If you can point me to an instance of a build failure, I will take a look at fixing this the right way, if possible.

viame/master on fletch is close to master, so both. Reproducing is low priority right now, won't happen for a bit