Re: Remove PEAR_Common::validPackageName()
| From: | Roman Neuhauser | Date: | Thu, 13 Nov 2003 13:04:36 +0000 |
| Subject: | Re: Remove PEAR_Common::validPackageName() | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23579@lists.php.net to get a copy of this message | ||
# mj@php.net / 2003-11-12 19:46:13 +0100:
> On Wed Nov 12, 2003 at 02:1642PM +0100, Sandro Zic wrote:
> > I opt for removing PEAR_Common::validPackageName().
>
> Huh, I object :).
>
> > Because it should be possible to name a package different compared to the
> > class prefix.
> >
> > For example:
> >
> > Someone (e.g. me) wants to name his packages in Java style:
> >
> > com.example.[package]
> >
> > If I do "pear package" on that, the package manager complains that the package
> > name is invalid because it does not match the class prefix. Of course, no one
> > would/could prefix his class with "Com.Example.Package_".
>
> We might instead add a command line options like "pear package
> --skip-name-validation" or something similar. How does that sound for you?
How about making it possible to swap in different package name
validator?
Not that I'm in favor of having all kinds of package names in PEAR,
but the framework has a long way to go if it wants to be usable
outside pear.php.net without considerable hacking.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html