On 11/09/2016 09:41 PM, GuimarĂ£es Faria Corcete DUTRA, Leandro wrote:
> 2016-11-09 18:30 GMT-02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>:
>> On 11/09/2016 09:02 PM, Leandro Guimaraes Faria Corcete DUTRA wrote:
>>>       Please make all DB drivers, or at least the Maria ones, only
>>> recommendations, not hard dependencies.
>>
>> I'm sorry to hear you don't like MariaDB packages.
> 
> Actually it is more that I do not see the need for it, even if it is
> true that I do not like Maria DB.  And I would like to keep my systems
> as lean as possible.

Then you need to build gdal yourself, on Gentoo perhaps. Because Debian
packages tend to enable as much features as possible, unlike Gentoo
where USE flags help to limit the features to just those you need.

>> GDAL is built with
>> MySQL/MariaDB support because ogr2ogr is one of the few viable options
>> to get spatial data into those databases. Hence the dependency on
>> libmariadbclient18 is required to not cause segfaults when using libgdal20.
> 
> I do not follow, why ogr2ogr would need MySQL or Maria DB, when all I
> want to use is PostGIS?

Because you are not the only user the gdal packages. See the recent
discussion about the MySQL/MariaDB support on the debian-gis list.

>> Having the libmariadbclient18 package installed does not hinder your use
>> of PostgreSQL for which libgdal20 depends on libpq5. GDAL interfaces
>> with many data sources, that includes several most people won't use.
>> It's just the nature of the library.
> 
> Several other packages have can interface with many data sources
> without needing to have an arbitrary one installed.

When linking to a library, a dependency on the respective library
package is required. Unless dlopen is used, which is not the case for
most GDAL drivers.

>> If don't want packages depending on MySQL/MariaDB packages, help make
>> PostgreSQL such an awesome database that people will not be able to
>> justify using something else.
> 
> It is already as far as I am concerned.

But other people are still not convinced, and are using MySQL/MariaDB
instead of PostgreSQL. You'll need to get those people to switch to
PostgreSQL before we can consider dropping support for MySQL/MariaDB in
GDAL.

>> That work includes patching many projects
>> to support PostgreSQL as a first class database backend to not have them
>> require MySQL/MariaDB as the only option.
> 
> You mean it is an arbitrary decision by the gDal developers that could
> simply be patched away?

You clearly don't understand. As long as people are using MySQL/MariaDB
instead of PostgreSQL there is demand for support of those databases in
GDAL, and hence for that support to be enabled in the gdal package in
Debian.

If you want to patch that away because you don't have the need for that
support, please do so in your fork of the package which only has to
support your needs. The gdal package in Debian needs to service the
needs of many more people than you. I have no need for the MySQL/MariaDB
support either, but I've re-instated the support after the MariaDB
packages were fixed on mips4el, because other users of the package do
have that need. And in Debian one of our priorities are our users, which
are many more people than just you and me.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Reply via email to