Re: PEAR Channels, draft 0.4

From: Date: Tue, 24 Feb 2004 02:31:40 +0000
Subject: Re: PEAR Channels, draft 0.4
References: 1 2  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-116@lists.php.net to get a copy of this message
Hi, Pierre-Alain Joye wrote:
- A name based on the master server, java-style (net.php.pear, net.php.pecl, org.horde.pear)
-1 Keep the obvious name used in the URI, as it is now. that's fine, so pear.php.net instead of net.php.pear
One thing we can add is a channels server. We can allow channels definitions on our server and then the clients can query through it via the installer and install/upgrade them. That will increase the visibility of non php.net projects. Yes, I would still want the ability to register a non-official channel, for people to test local channel distributions, or to implement intranet channels
Adding a default channel to use is better imo. The "search everywhere" can be very dangerous and hasardeous. Yes, that's fine
What is the goals of the subchannels? I really miss the usage. QA does not require sub channels. And we can create a channel for specific usages like the tests suite. The main feature of channels that I believe is REALLY important is that any collisions of files between channels is not allowed. In other words, an upgrade that collides with files from another channel is unacceptable.
INSERT INTO channels (id, parent, name, summary, server, installroot) VALUES(2, 0, 'PHP PHP Extension Community Library', 'pecl.php.net', ''); installroot) VALUES(3, 1, 'PHP Extension and Application Repository, QA channel', 'qa.pear.php.net', '');
I'm really not sure it's a good idea to split pecl/pear as two distinct channels, at least as a default behavior. After the channels activations, pe(ar|cl)web should work exactly as now, with or without channels client on the client side. I find it confusing to use the pear command to install pecl packages - there should be a new command named pecl that only installs pecl packages, and it would be best to separate the two databases anyways - we'll want different channels for php5 and php4 binary extensions, among other things, and the channels that relate to PEAR need not relate to PECL. They are logically separate, why force them to be the same? However, if we don't split out the pecl command, then I agree behavior should remain the same. I do think it would make more sense in the long run to separate PHP code from C code, my 2 cents.
add packagelist.xml which is a listing of all packages in a source channel. It contains all the <package> tags for every release available in the channel (perhaps an abbreviated version with only the package name, summary, relative path to the .tgz, and dependencies to save space?)
Space is not an issue imho. Besides the little things to discuss, can you send me the code you have for pearweb? I like to commit it but maybe not under the current pear-databases stuffs. There is many things to update before commiting this huge change. Hold your fingers for a short time :) I'd love to. I'm on the road, and since it isn't CVS-ized, I can't access it here, but when I get a chance, I will move development to the laptop so that isn't a problem. The code is very much pre-alpha though, so don't be alarmed :). It works, but I'm sure the design will change as we get to know the problem better.


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