Re: Re: channel naming conventions
| From: | Greg Beaver | Date: | Tue, 17 Aug 2004 12:36:09 +0000 |
| Subject: | Re: Re: channel naming conventions | ||
| References: | 1 | Groups: | php.pear.dev php.pear.core |
| Request: | Send a blank email to pear-dev+get-32735@lists.php.net to get a copy of this message | ||
Mika Tuupola wrote:
On Sat, 14 Aug 2004, Davey wrote:Hi Mika, Welcome back. No worries - it is my goal to allow humans to take care of the political issues, and the installer to take care of technical ones. I feel pretty strongly that this is both a political issue, and that solutions must not be forced on everyone. Fortunately, for those who do wish to force a solution on everyone in their own channel, there is a technical solution. If a channel wishes to require a prefix (or any other convention), the place to do this will be in the validation package. The validation package would allow verification of prefix both at package time and at install time. So, on a per-channel basis, this can easily be implemented, for those who are concerned about it. The (totally incomplete) PEAR_Validate class is the skeleton of the base class for a validation package, and is unrelated to the Validate package we see through PEAR. PEAR_Validate has 1 purpose: validating a package release, package name for downloading a release, and other activities surrounding an actual package .tgz GregDoes the installer take care of this Crtx/ dir? or should I make Crtx/Template the base install dir?Please no channel prefixes on categories. This takes away possibility of using alternative channels as a drop in replacement for existing package.