Re: [Mageia-dev] Adding additional provides to php database modules
Am Mittwoch, 28. Dezember 2011, 17:01:17 schrieb Guillaume Rousse: Le 19/12/2011 03:02, Thomas Spuhler a écrit : Could you please explain a little more what you are looking for. PHP provides the php-mysql and php-pdo-mysql He wants to add a php-database virtual package, provided by the different php database bindings. Exactly. So mediawiki and drupal could just require php-database or something like that. The only problem here is that, pdo aside, there is no unified database interface in php. Some applications may have explicit support for some databases, this doesn't mean they have generic support for any database. You're likely to quickly run into applications able to work with mysql, postgresql or sqlite, and those able to work with just mysql or postgresql. In theory, you'll end up with as much virtual package as potential combination. I see the problem. So it would be actually better for each application like drupal and mediawiki to have its own virtual provides for the database packages (like drupal already does). Thanks, Oliver
Re: [Mageia-dev] Adding additional provides to php database modules
Le 04/01/2012 20:08, Oliver Burger a écrit : The only problem here is that, pdo aside, there is no unified database interface in php. Some applications may have explicit support for some databases, this doesn't mean they have generic support for any database. You're likely to quickly run into applications able to work with mysql, postgresql or sqlite, and those able to work with just mysql or postgresql. In theory, you'll end up with as much virtual package as potential combination. I see the problem. So it would be actually better for each application like drupal and mediawiki to have its own virtual provides for the database packages (like drupal already does). pedantism virtual provides doesn't means anything, because there isn't any physical provides. You're speaking of a virtual package here. /pedantism I just had a look at the solution implemented in drupal package. The drupal-mysql and drupal-postgresql packages seems wrong, because they enforces a dependency against a local database, whereas it should only requires the correct pdo package. This small issue aside, the whole idea seems quite overkill for me: it is really useful to add 3 empty packages just to handle this interactively, whereas documenting the issue would be as much efficient ? BTW, the PDO case is precisely the one for which the package-specific solution is not needed: any PDO compliant database should work, as PDO is an abstraction layer :) -- BOFH excuse #295: The Token fell out of the ring. Call us when you find it.
Re: [Mageia-dev] Adding additional provides to php database modules
On Saturday, December 17, 2011 03:24:16 PM Oliver Burger wrote: Hi, I'm maintaining mediawiki and drupal. Both packages require a php database module but both can work with mysql, postgresql and sqlite. Now the mediawiki package does simply require both php-mysql and php-pgsql, which is bad since it leads to installing unneeded database libraries in the system. Drupal has three sub packages which doe require the respective php database module and one of the three is required by drupal itself, which is some kind of ugly workarround. I think it would be a cleaner solution to have php-X providing something common and php-pdo_X providing something common (X being one of mysql, pgsql or sqlite). What do you think? I tried contacting the php maintainer by mail, but he didn't answer me. Oliver Could you please explain a little more what you are looking for. PHP provides the php-mysql and php-pdo-mysql -- Best regards Thomas Spuhler
Re: [Mageia-dev] Adding additional provides to php database modules
Le 19/12/2011 03:02, Thomas Spuhler a écrit : Could you please explain a little more what you are looking for. PHP provides the php-mysql and php-pdo-mysql He wants to add a php-database virtual package, provided by the different php database bindings. The only problem here is that, pdo aside, there is no unified database interface in php. Some applications may have explicit support for some databases, this doesn't mean they have generic support for any database. You're likely to quickly run into applications able to work with mysql, postgresql or sqlite, and those able to work with just mysql or postgresql. In theory, you'll end up with as much virtual package as potential combination. -- BOFH excuse #276: U.S. Postal Service
Re: [Mageia-dev] Adding additional provides to php database modules
Am Samstag, 17. Dezember 2011, 18:30:56 schrieb Thomas Spuhler: On Saturday, December 17, 2011 03:24:16 PM Oliver Burger wrote: I think it would be a cleaner solution to have php-X providing something common and php-pdo_X providing something common (X being one of mysql, pgsql or sqlite). What do you think? I tried contacting the php maintainer by mail, but he didn't answer me. Oliver Because he is trying to get php-gkt2 built :) Ok :) And what about my change request? Oliver
Re: [Mageia-dev] Adding additional provides to php database modules
On Sunday, December 18, 2011 02:36:42 AM Oliver Burger wrote: Am Samstag, 17. Dezember 2011, 18:30:56 schrieb Thomas Spuhler: On Saturday, December 17, 2011 03:24:16 PM Oliver Burger wrote: I think it would be a cleaner solution to have php-X providing something common and php-pdo_X providing something common (X being one of mysql, pgsql or sqlite). What do you think? I tried contacting the php maintainer by mail, but he didn't answer me. Oliver Because he is trying to get php-gkt2 built :) Ok :) And what about my change request? Oliver That comes after php-gtk2. php-gtk2 doesn't build right now and the current version trows out a lot of errors. -- Best regards Thomas Spuhler
[Mageia-dev] Adding additional provides to php database modules
Hi, I'm maintaining mediawiki and drupal. Both packages require a php database module but both can work with mysql, postgresql and sqlite. Now the mediawiki package does simply require both php-mysql and php-pgsql, which is bad since it leads to installing unneeded database libraries in the system. Drupal has three sub packages which doe require the respective php database module and one of the three is required by drupal itself, which is some kind of ugly workarround. I think it would be a cleaner solution to have php-X providing something common and php-pdo_X providing something common (X being one of mysql, pgsql or sqlite). What do you think? I tried contacting the php maintainer by mail, but he didn't answer me. Oliver
Re: [Mageia-dev] Adding additional provides to php database modules
On Saturday, December 17, 2011 03:24:16 PM Oliver Burger wrote: Hi, I'm maintaining mediawiki and drupal. Both packages require a php database module but both can work with mysql, postgresql and sqlite. Now the mediawiki package does simply require both php-mysql and php-pgsql, which is bad since it leads to installing unneeded database libraries in the system. Drupal has three sub packages which doe require the respective php database module and one of the three is required by drupal itself, which is some kind of ugly workarround. I think it would be a cleaner solution to have php-X providing something common and php-pdo_X providing something common (X being one of mysql, pgsql or sqlite). What do you think? I tried contacting the php maintainer by mail, but he didn't answer me. Oliver Because he is trying to get php-gkt2 built :) -- Best regards Thomas Spuhler
