Opened 9 years ago
Closed 9 years ago
#6172 closed task (fixed)
Remove pcidsk old driver or document why it is still needed
Reported by: | Kurt Schwehr | Owned by: | Kurt Schwehr |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | svn-trunk |
Severity: | normal | Keywords: | cleanup |
Cc: |
Description
Is there something the new driver can't do that the old driver can do?
If not, can I delete the old driver and the config option for the old driver?
A side question is why can't this driver be disabled? Do other drivers use it is somehow such that GDAL can't live without it?
Change History (5)
comment:1 by , 9 years ago
follow-up: 3 comment:2 by , 9 years ago
I was just meaning that is there another driver that requires pcidsk to always be compiled in? The current behavior of --without-pcidsk compiles in the pcidsk old. GDAL_SKIP probably works just fine, but I have not tested it.
comment:3 by , 9 years ago
Replying to goatbar:
I was just meaning that is there another driver that requires pcidsk to always be compiled in?
No
comment:5 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I see no compelling reason not to remove the old pcidsk driver.
I am not sure what you mean about it not being disable-able. Doesn't GDAL_SKIP work with it?