Re: channels RFC 0.5 on the wiki
| From: | Greg Beaver | Date: | Tue, 02 Mar 2004 16:33:57 +0000 |
| Subject: | Re: channels RFC 0.5 on the wiki | ||
| References: | 1 2 3 4 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-143@lists.php.net to get a copy of this message | ||
Hi Jon,
I guess things go full circle :). The original channels RFC had exactly what you're describing, and there was unanimous opposition.
I do think that it would be best to use the default server name as the channel name for most situations, however, as it will help users to figure out where a random package is from when installing a new application that uses a custom channel, for instance.
I think the internal implementation you describe is exactly what is needed
Greg
Jon Parise wrote:
On Thu, Feb 26, 2004 at 11:34:41PM -0500, Greg Beaver wrote:The solution is to set up a mirror property. I know Pierre-Alain wishes to delay this consideration a bit, and I do agree we will need to get the core working first before allowing mirrors, but the process should probably be worked out before the code is anyways. However, it is essential for namespace resolution that channel name be part of the package name somehow. Otherwise we will also have a global name registry, which will be a nightmare to maintain.I gave this some thought, and I agree with you. I needed to think of the channel name more of a namespace and less of a site identifier. I suppose my initial confusion arose due to the fact that the your channel name is essentially a hostname. Given that, I think it would be smart to be sure that we differentiate between "channel" and "distribution site" from the very beginning. A modified version of your proposed system might look like this: <dep rel="has" channel="horde" type="pkg">Example</dep> We now have a channel named "horde" (or some other unique name). The PEAR Installer would maintain some kind of mapping between channel names and distributions sites. array('pear' => 'pear.php.net', 'pecl' => 'pecl.php.net', 'horde' => 'pear.horde.org') This would make it easy to override a channel's distribution site at runtime, and it lends itself nicely to mirroring, e.g.: array('pear' => array('pear.php.net', 'pear.mirror.org')) (If the first site is unavailable, we'll try the second site, and so on.) The "stock" PEAR Installer would ship with some known channel mappings pre-configured (such as the above list), and it would trivial for the site administrator to add a new channel mapping to their local PEAR installation ('pear add-channel channel site'). Or perhaps there could be a command to fetch the channel mappings from some master channel registry on pear.php.net ('pear update-channels').