Re: PEAR2 standards: why src/ instead of lib/?
| From: | Igor Feghali | Date: | Wed, 05 Mar 2008 04:29:37 +0000 |
| Subject: | Re: PEAR2 standards: why src/ instead of lib/? | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-49260@lists.php.net to get a copy of this message | ||
> Okay, but if part of the point of PEAR2 is unzip-and-go, then this
> means that you then *must* be including files from src/, which is what
> seems semantically wrong to me. If the package provides library files,
IMHO talking about "source" is acceptable here as we are talking about
scripting language. For languages like C, for instance, it makes sense
to separate source code, library and program. But in our case those
three stuff can be confused into the same thing. Just my 2 cents.
regards,
iGor.