Re: channels RFC 0.5 on the wiki
| From: | Jon Parise | Date: | Fri, 27 Feb 2004 03:40:52 +0000 |
| Subject: | Re: channels RFC 0.5 on the wiki | ||
| References: | 1 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-132@lists.php.net to get a copy of this message | ||
On Thu, Feb 26, 2004 at 01:32:56AM -0500, Greg Beaver wrote:
>
> http://pear.dnsalias.net/wiki/view.php?wiki=PearCore&page=PearChannels#
The Wiki appears to be broken right now:
YAWP_ERROR WARNING [Unknown modifier '('] in file
[/Users/pmjones/Sites/pmjones.dnsalias.net/PEAR/Text_Wiki/Text/Wiki/Rule/url.php] at line [139]
... so I can only go by the contents of this email for right now.
> Also, a few enhancements to the way channels are listed in package.xml
>
> <name channel="pear.php.net">Log</name>
>
> No need to parse the channel name out. That would be stupid, since some
> external apps like Zzoss use . in package.names.
>
> Same in the dependency
>
> <dep rel="has" channel="pear.horde.org"
> type="pkg">Example</dep>
I don't think I like the requirement that a package know about its own
channel. I think this detracts from the channel system's flexibility.
For example, someone might want to set up a local package server
(e.g., pear.company.com) that mirrors certain sanctioned releases of
packages. For this to work, the package.xml files would have to be
rewritten (and the packages rebuilt) for use on the local server.
I don't know how else to represent a package's channel association,
though.
I suppose my use case could be satisfied by a set of overriding
command line options, but I don't think we're at the point where we
want to see that as the solution while the initial channels design is
still so malleable.
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)