Re: Re: channel naming conventions
| From: | Greg Beaver | Date: | Sat, 14 Aug 2004 18:35:43 +0000 |
| Subject: | Re: Re: channel naming conventions | ||
| References: | 1 2 3 | Groups: | php.pear.dev php.pear.core |
| Request: | Send a blank email to pear-dev+get-32668@lists.php.net to get a copy of this message | ||
Jon Wood wrote:
Personally I think that the installer should take care of this, to prevent rougue channels overwriting files from other channels - otherwise I could see some interesting hacks coming up in the future.This is moot - the installer already checks for file conflicts (although it wasn't working until I fixed it a months ago) in every PEAR version. Incidentally, I was not talking about package naming or file naming, only the channel name. A channel can devise its own scheme for coding standards and naming independent of anything we decide here. Obviously, PEAR needs to make recommendations to keep things running smoothly, but the whole point of channels is to decentralize control while promoting inter-operability. Greg