Re: channels RFC 0.5 on the wiki

From: Date: Tue, 02 Mar 2004 18:07:26 +0000
Subject: Re: channels RFC 0.5 on the wiki
References: 1 2 3 4 5 6  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-145@lists.php.net to get a copy of this message
Hi, Since I personally prefer what Jon is saying, is there any opposition now that we are at a future date? It would add one element to the channel.xml file, <servers>. Sub-elements <source> would contain the server name, and this wil allow future upgradability <source type="server">pear.php.net</source> future possibilities: <source type="archive">/path/to/archive.tgz</source> <source type="database">dsn://stuff</source> etc. If this is OK, I'll update the RFC. Greg Jon Parise wrote:
On Tue, Mar 02, 2004 at 11:33:57AM -0500, Greg Beaver wrote:
I guess things go full circle :). The original channels RFC had exactly what you're describing, and there was unanimous opposition.
Sorry; I wasn't around for the first revision of the proposal.
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
Sure, if people want the channel name to be 'pear.example.com', then fine. I just want to be able to remap it to a different distribution site without modifying the package.xml file and rebuilding the package. Still, I don't think that anyone will have any trouble understanding that the 'pear' channel comes from a PEAR package server and a 'horde' channel comes from a Horde package server. To take my experience with something like the FreeBSD ports system, I generally don't care *where* the distribution archives are located, as long as the system can find them and I can force a different location if I want.


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