[GRASS-dev] [gdal-dev] Moving GDAL GRASS driver in a dedicated repository ?

[Even Rouault]

Hi Markus,

looks good to me. So maybe now you can send a pull request to remove the 
drivers from OSGeo/GDAL and modify 
https://gdal.org/drivers/raster/grass.html & 
https://gdal.org/drivers/vector/grass.html to point to the new repo ? 
I'd like to issue a 3.5.0 release candidate this week.

Even

Le 28/04/2022 à 22:31, Markus Neteler a écrit :
> Hi Even,
>
> (back to your wish)
>
> On Thu, Nov 18, 2021 at 7:12 PM Even Rouault <even.rouault at spatialys.com> wrote:
>> Hi,
>>
>> (writing to both GDAL and GRASS lists)
>>
>> Working on the transition to CMake as the GDAL build system, the
>> particular status of the GRASS driver in GDAL raised my attention.
>>
>> (The following is based on my understanding. It has been ages since I
>> didn't try this...)
>>
>> This driver is a bit odd in the sense that there's a cyclic dependency
>> to work around, as GRASS links to GDAL , but the GDAL GRASS driver needs
>> to be linked against GRASS.
>>
>> So the usual procedure is:
>>
>> - build GDAL without the GRASS driver
>>
>> - build GRASS against GDAL
>>
>> - build the GDAL GRASS driver from the separate gdal-grass tarball that
>> GDAL distributes along its main tarball.
>>
>> With the current GDAL autoconf build system, there's also the
>> possibility to rebuild GDAL with the GRASS driver builtin in libgdal,
>> but that's a bit odd, since you need to make sure that this new libgdal
>> is the one that GRASS will link against at runtime, otherwise chaos will
>> ensure. I'm not sure if that's used. This is typically something I would
>> *not* want to support in the new GDAL cmake build.
>>
>> All in all, given the particular nature of that driver, I believe it
>> would be better in a dedicated repository, with its standalone build
>> scripts, whose initial version could be just the ones of
>> https://github.com/OSGeo/gdal/tree/master/frmts/grass/pkg, or evolve to
>> CMake or whatever the maintainers of that driver would prefer. I believe
>> this would make the situation clearer.
>>
>> Opinions ? and people interested in setting up that dedicated repository ?
> Yes and finally done that:
>
> https://github.com/OSGeo/gdal-grass
>
> Hope I got it right (history is preserved, I used
>
> git filter-repo --path ogr/ogrsf_frmts/grass --path frmts/grass
>
> and then moved the remaining needed files into the toplevel directory.
> Hope I got it right.
>
> Markus
>
-- 
http://www.spatialys.com
My software is free, but my time generally not.