Bearing in mind that I use none of the drivers on Even's list, I find his suggestion and reasoning compelling. I especially agree with his comment that the only way to get anyone's attention is to break their workflow, if only temporarily. The main risk here is that a program that uses gdal (eg, QGIS) might hide this from it's users by setting the options in code. Of course, when it truly breaks then this program will have deal with unhappy users, so the burden will be on them, not on gdal devs (we can only hope).

As to the "cemetery" as Even calls it, this is in line with my thinking before I saw Even's message. GIT maintains history, so anyone wanting an old driver can always revert back to older versions (at the cost of losing new capabilities.) I would consider that instead of just noting in this in the docs somewhere, an attempt to load a removed driver will result in a message that says "This driver was removed in GIT update xxxx" to make it easier to track down. A  variation on this that would require a little more work is to replace each removed driver with a stub that prints an appropriate failure message. In most cases, this would be the same "this was removed" message, but in the rare case that someone else picks up maintenance of the driver, the message could be something like  "This driver is independently maintained at <URL>".
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to