Re: channels RFC 0.5 on the wiki
| From: | Greg Beaver | Date: | Fri, 27 Feb 2004 04:34:41 +0000 |
| Subject: | Re: channels RFC 0.5 on the wiki | ||
| References: | 1 2 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-133@lists.php.net to get a copy of this message | ||
Hi Jon,
All valid concerns.
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.
So, if we look at it as a problem of namespace, the question becomes how do you define namespace within channels?
Perhaps the real solution is not to worry about it at all :). People will consider PEAR to be the end-all-be-all namespace (Log is PEAR::Log). Those who wish to have their packages co-exist with PEAR packages will have to do a name prepend (Horde_Log). In this way, there would not need to be a modification to <name> in package.xml at all, just a naming convention that is php-wide.
We could make as a condition of being an official public channel that all packages have a prepend so there is no risk of namespace clashing.
However, the <dep> tag would still need channel information
<dep rel="has" type="pkg" channel="foo.example.com">Foo_Log</dep>
How's this sound?
By the way, it seems the wiki is back up and running
Greg
Jon Parise wrote:
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.