Re: PEAR channel server for applications and libraries outside PEAR

Sebastian Nohn wrote: > Justin Patrin wrote: >> On 6/1/07, Sebastian Nohn <sebastian@nohn.net> wrote: >>> Greg Beaver wrote: >>>> Sebastian Nohn wrote: >>>>> Hi Christian, >>>>> >>>>> Christian Weiske wrote: >>>>> >>>>>> PEAR is the best method to distribute PHP libraries, and since it >>> also supports multiple channels, also a very convenient way to >>> distribute PHP applications. >>>>>> Some apps already have their own channel server (e.g. Geeklog, >>> http://pear.geeklog.net/ ), other apps and libs do have >>> PEAR-installable packages, but don't want to set up and maintain a >>> complete channel server (e.g. OpenID libraries, >>> http://www.openidenabled.com/openid/libraries/php ). >>>>>> The ideal place for those projects would be a dedicated PEAR >>> channel server that is open for everyone. pearified.com has been >>> started as such a project, but the lead, Clay Loveless, does not >>> respond to any emails. >>>>>> Suggestions, ideas, volunteers? >>>>> I think, first the pear command line tool should be able to perform >>> all >>>>> end user commands in a comfortable way on different channels. >>>> pear config-set default_channel whatever.com >>>> >>>> then all end user commands will work identically to the way they work >>>> for pear.php.net. >>>> >>>> (This has worked since PEAR 1.4.0 FYI) >>> Do you call that comfortable? >>> >> THere's always pear upgrade channel://package as well. It is a reality >> that multiple channels can have packages names the same, hence the >> need for disambiguation via the channel name. > > # pear upgrade phpunit/phpunit > Nothing to upgrade This is a known bug in the current stable release of PEAR. I'm working hard to get the details worked out for the next release, one I hope to make a week from now. The same problem occurs with packages in the PEAR channel, it has nothing to do with channels, intuition, or annoyance thereof :). > That is not very intuitive. What if I want to upgrade the whole channel? > Or list all packages in a channel? Or just upgrade all packages, no > matter what channel they are in? upgrade-all does upgrade all packages regardless of channel, and "pear help upgrade" shows options to specify a specific channel. Sebastian, I'm not trying to defend bugs in the PEAR installer, on the contrary, I would like to fix them. It is also entirely possible that you have envisioned another way of working with the installer that has not occurred to me. This is the wrong time for me to ask perhaps, but your feedback *will* result in improvements to the PEAR installer. My frustration is only that I would like it to work perfectly for everyone on the first try, and when it doesn't, I'd like to be able to fix it. Sometimes this isn't possible and that is also my curse. Greg