Bug#390570: [php-maint] Bug#390570: php5-mysql: circular dependency hell
Steve Langasek schrieb: On Tue, Oct 03, 2006 at 12:58:09PM +1000, Adam Conrad wrote: There is a circular dependency between php5-mysql and php5-mysqli: php5-mysql :Depends: php5-mysqli (= 5.1.6-2) php5-mysqli :Depends: php5-mysql (= 5.1.6-2) Color me confused; why do we need two modules for this anyway? That seems rather bletcherous. The mysql and mysqli module use different APIs, whoever is using the old API (which many OS webapps do) needs the mysql module, while anyone wanting to take full advantage of the more advanced MySQL features from MySQL 5 needs to use the new mysqli module with the new API. Both modules can happily coexist in the same apache instance. Regards, Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390570: [php-maint] Bug#390570: php5-mysql: circular dependency hell
hey guys, On Tue, 2006-10-03 at 14:52 +0200, Sven Mueller wrote: Steve Langasek schrieb: On Tue, Oct 03, 2006 at 12:58:09PM +1000, Adam Conrad wrote: There is a circular dependency between php5-mysql and php5-mysqli: while i know circular dependencies are generally frowned upon, i was under the impression that they're allowed for binaries from the same source package, correct? or maybe my brain is totally fabricating that memory... it's been known to do that. Color me confused; why do we need two modules for this anyway? That seems rather bletcherous. there are two reasons behind the split from what i can tell. 1 - sync closer to ubuntu. for all practical purposes, ubuntu has been leading the php packaging (s/leading/the only one doing until recently/ if you will), so the better we can stay in sync with them the better. this is of course the weaker of the two arguments :) 2 - there's no way currently to package the two modules together in the same binary package without causing quite a bit of packaging grief wrt the code handling the php modules. this is the real reason, and also why ubuntu has already done this. as soon as i send this email, i'm going to immediately start poking at adam to commit his stuff into svn, and i'll see if i can take whatever last steps/testing etc are needed to make this a moot issue. The mysql and mysqli module use different APIs, whoever is using the old API (which many OS webapps do) needs the mysql module, while anyone wanting to take full advantage of the more advanced MySQL features from MySQL 5 needs to use the new mysqli module with the new API. Both modules can happily coexist in the same apache instance. which is neither an argument for or against the current setup, though. i.e.: ideally nothing would break if they were packaged together or seperately, except for the above mentioned stuff. sean signature.asc Description: This is a digitally signed message part
Bug#390570: [php-maint] Bug#390570: php5-mysql: circular dependency hell
On Tue, Oct 03, 2006 at 05:04:15PM +0200, sean finney wrote: hey guys, On Tue, 2006-10-03 at 14:52 +0200, Sven Mueller wrote: Steve Langasek schrieb: On Tue, Oct 03, 2006 at 12:58:09PM +1000, Adam Conrad wrote: There is a circular dependency between php5-mysql and php5-mysqli: while i know circular dependencies are generally frowned upon, i was under the impression that they're allowed for binaries from the same source package, correct? Neither dpkg, apt or aptitude even look at source packages names when installing binary packages, so being from the same source package have no effect on the issue. Though this might affect testing propagation. The mysql and mysqli module use different APIs, whoever is using the old API (which many OS webapps do) needs the mysql module, while anyone wanting to take full advantage of the more advanced MySQL features from MySQL 5 needs to use the new mysqli module with the new API. Both modules can happily coexist in the same apache instance. which is neither an argument for or against the current setup, though. i.e.: ideally nothing would break if they were packaged together or seperately, except for the above mentioned stuff. Even if you keep the two packages, does php5-mysqli really need to depend on php5-mysql ? People installing php5-mysqli instead of php5-mysql probably know what they are doing. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390570: [php-maint] Bug#390570: php5-mysql: circular dependency hell
On Tue, Oct 03, 2006 at 02:52:58PM +0200, Sven Mueller wrote: Steve Langasek schrieb: On Tue, Oct 03, 2006 at 12:58:09PM +1000, Adam Conrad wrote: There is a circular dependency between php5-mysql and php5-mysqli: php5-mysql:Depends: php5-mysqli (= 5.1.6-2) php5-mysqli :Depends: php5-mysql (= 5.1.6-2) Color me confused; why do we need two modules for this anyway? That seems rather bletcherous. The mysql and mysqli module use different APIs, whoever is using the old API (which many OS webapps do) needs the mysql module, while anyone wanting to take full advantage of the more advanced MySQL features from MySQL 5 needs to use the new mysqli module with the new API. Both modules can happily coexist in the same apache instance. Ok, upstream retardation, par for the course. Understood, thanks. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390570: [php-maint] Bug#390570: php5-mysql: circular dependency hell
On Tue, Oct 03, 2006 at 12:58:09PM +1000, Adam Conrad wrote: There is a circular dependency between php5-mysql and php5-mysqli: php5-mysql :Depends: php5-mysqli (= 5.1.6-2) php5-mysqli :Depends: php5-mysql (= 5.1.6-2) Circular dependencies, while often incorrect and hellish on upgrades, are not always a bug. The dependency loop will happily be broken by the package management tools, and since the maintainer scripts of these packages don't depend on each other, it's not a practical problem, just an aesthetic one. What is the purpose to have both packages if users are requested to install both of them anyway? The point is that, in the future, we intend to ship both modules in one package with the New And Improved config setup, and this is the easiest way to ensure future upgrade paths remain sane for people who install from the old config setup and later upgrade to the shiny new one. For the record, php5 has shipped this way in Ubuntu since before the dapper release, and it's neither generated a single problem report, nor a single complaint. Color me confused; why do we need two modules for this anyway? That seems rather bletcherous. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
