Re: Re: channel naming conventions
| From: | Jon Wood | Date: | Sat, 14 Aug 2004 17:30:19 +0000 |
| Subject: | Re: Re: channel naming conventions | ||
| References: | 1 2 | Groups: | php.pear.dev php.pear.core |
| Request: | Send a blank email to pear-dev+get-32666@lists.php.net to get a copy of this message | ||
On Sat, 14 Aug 2004 12:49:52 -0400, Davey <davey@php.net> wrote:
> Greg Beaver wrote:
> > Hi,
> >
> > We need to come up with naming conventions for channels to help avoid
> > conflicts. A prefix could be used to distinguish private channels from
> > official channels. We could require all private channels to prefix with
> > "_", as in "_chiara" for the random private channel that distributes
> > packages for the unofficial "chiara" channel located somewhere in Italy.
> > This would avoid any confusion with the "chiara" channel for the
> > unrelated public channel that is (will be) registered at pear.php.net.
> >
> > Alternately, we could recommend that all private channels be named after
> > their server as in "chiara.example.it" and only public servers would be
> > given nicknames that differ from their server. This seems most
> > practical to me.
> >
> > Any brighter ideas?
> >
> > Greg
>
> What about doing 2 things:
>
> 1) Maintain a channel registry on pear.php.net
> 2) Allow the user to specify the prefix on install to avoid conflict.
>
> I do have a question, all channel packages should be called:
>
> Channel_Category_Package right?
>
> And are installed in $php_bin/Channel/Category/Package.php ??
>
> So, for example, I would have:
> Crtx/Template/Parser.php
>
> Does the installer take care of this Crtx/ dir? or should I make
> Crtx/Template the base install dir?
>
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.
> - Davey
>
>
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>