On Sat, Sep 02, 2023 at 11:19:54AM -0400, Dave Cramer wrote:
> On Sat, 2 Sept 2023 at 06:27, Devrim Gündüz <devrim@gunduz.org> wrote:
>> Do you have a timeline for these? I can see that there are several
>> people in the mailing list (not me) to step up the plate and help fix
>> the issues. Would you consider moving project to Github, so that people
>> can send PR and you can merge them, if you don't have time to fix them
>> all?
>
> I'd certainly be a proponent of moving to github and helping out maintain
> this.
That would be like a big change, still if that helps in keeping the
project more healthy than it is now, why not. From what I can see,
this driver's development has been let aside.
Saito-san and Inoue-san have done a good job over the years spending
cycles on maintaining that. The question is who could actually take
care of the basic maintenance of the driver? I do have a little bit
of experience with the ODBC code base in the history of the project in
the 2015~2017 area with its core code and the regression tests as
VMware was relying heavily on it back these days. So I could handle a
few of the compatibility changes to keep the thing able to build and
pass the tests, but my experience feels kind of limited. Or it's just
that everybody has zero experience with it and I'm one with the most
experience :)
I was just quickly testing a build, and Debian does not offer
odbc_config that would be in unixodbc, but iodbc is able to build.
I recall that it was slightly easier to work on this stuff with
homebrew under MacOS, actually..
--
Michael
