Re: solution for those depending on PEAR packages with non-PEAR

Pierre-Alain Joye wrote:

On Sat, 23 Apr 2005 21:15:56 +0200 lsmith@php.net (Lukas Smith) wrote:

but this is exactly what will happen today .. or what is happening today. this solution gives you the possibility to make a temporary fork that is clearly marked as such until a general solution is found and the maintainer has found the time to make another release.

Use force, install it using your home packaged version, but temporary solutions exist.

ok what you are suggesting are solutions outside of the installer. not very scalable. what i want to be able to do is make a new release of my package and be done with it. and my users want to install packages with the installer, relying one me to set the proper dependencies. of course there is an alternative. i can publish the patched version in my channel. then the user will have to resolve the conflict. actually i dont know how the installer handles things if someone releases a package with the same name as an installed packaged in a channel that is checked before the channel of that package. all in all i think greg's solution makes it very transparent for every one involved what is going on. all of the other solutions require alot of communication and manual decision making about things the user doesnt understand ("there is a conflict between package xyz from channel foo and channel bar" is much less clear as in "channel foo had released a patched version for package xyz of channel bar that package abc depends on"). it also means that i have published a fork on my channel which makes it a much more permanent thing than just a file that is referenced by an URI in a package.xml dependency to get a quick fix out of the door. regards, Lukas