Re: dependencies and channels

From: Date: Fri, 02 Jul 2004 13:06:36 +0000
Subject: Re: dependencies and channels
References: 1 2  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-415@lists.php.net to get a copy of this message
Greg Beaver wrote:
Lukas Smith wrote:
Hi, I havent really read all the channel stuff in detail but I am wondering how dependency handling will work across channels? Do we just assume that package Foo from channel A depending on package Bar will be fullfiled by package Bar from channel B? Do we expect channels to specifically announce their "claimed" compatibility with other channels. Like channel A can claim compatibility to channel B?
I'm not sure I understand the question, but I'll try to answer it. Currently, dependency channels are very rigid and here's how it works <dep type="pkg" rel="has">Blah</dep> is ALWAYS pear::Blah channel must be explicitly specified if it is a non-PEAR channel <dep type="pkg" rel="has" channel="foo">Blah</dep> If a channel does not exist (is not registered locally as existing), there is an error. If the package does not exist in the channel, there is an error. channel_path has been completely removed - it only adds headache. You really must know where you intend to download code from, that can't be left to chance the way include_path is. However, it might be neat to work out a central server that spiders channels to get the list of packages and allows easy web searching for packages. This should be independent of the installer, in my opinion. Greg
the thing is some channels might be trying to be compatible .. others may not. so for example if i have a company internal channel of modified pear packages i would like to make my installer understand this. however i still may use channels which are not pear compatible which have packages with the same name. regards, Lukas

« previous php.pear.core (#415) next »