Re: updated channels rfc
| From: | Jon Parise | Date: | Tue, 02 Mar 2004 19:55:37 +0000 |
| Subject: | Re: updated channels rfc | ||
| References: | 1 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-148@lists.php.net to get a copy of this message | ||
On Tue, Mar 02, 2004 at 01:37:30PM -0500, Greg Beaver wrote:
> Here's the updated RFC, critique away
>
>
> http://pear.dnsalias.net/wiki/view.php?wiki=PearCore&page=PearChannels
I think this discussion may have happened earlier, but I think I'd
prefer this channel+package syntax:
pear install channel::package
(e.g., 'pear install horde::Log')
1. This syntax is more natural in that it mimics the way that PHP
notates namespaces.
2. The proposed use of the '/' (e.g., 'channel/package') connotes
"filesystem" to me. It's conceptually ambiguous with installing a
package from the local filesystem.
The fact that the PEAR installer would parse this format, notice
that there's no file extension, and then pull the package from a
network resource instead is too much magic for me. (I do realize
that this is how 'pear install package' works today, but I think
this goes a little too far.)
Also, it might be nice to support filesystem-based channels at some
point in the future. For example:
pear register-channel mychannel /stuff/pear/mychannel MyInstallRoot
I don't think we need to build that right now, but I'd like to at
least leave that door open.
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)