Re: Registering PECL pear web
| From: | Stig S. Bakken | Date: | Sun, 22 Dec 2002 01:37:53 +0000 |
| Subject: | Re: Registering PECL pear web | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-11790@lists.php.net to get a copy of this message | ||
On Wed, 18 Dec 2002, Michael Bretterklieber wrote:
> Hi,
>
> Mika Tuupola wrote:
>
> >On Wed, 18 Dec 2002, Michael Bretterklieber wrote:
> >
> >
> >
> >>I would like to register my radius-PECL with the pear-web
> >>(http://pear.php.net/package-new.php).
> >>
> >>What should I choose as package name? Radius or NET_Radius?
> >>
> >>PECL's have no category, should I choose Networking here?
> >>
> >>
> >
> > This bring me to another question. How do we differ
> > PECL packages on pearweb? Currently you can
> > only guess from different naming scheme (for example
> > mailparse http://pear.php.net/package-info.php?pacid=143)
> >
> > I think people should be able to easily see which packages
> > need compiling and which dont.
> >
> maybe we should add a <type> entity to the package.xml?
> <type>PECL</type>
> or
> <type>PHP</type>
The "package type" determines which package naming standard is used, so
this is not such a bad idea. But if the purpose is just to see whether
installing a package requires compiling C/C++ code, the presence of "src"
files is enough.
There are more similar package types that need handling in the future
(applications, Gtk components, pre-built extensions), I'll have to go into
the thinking box on this one.
- Stig