Re: PEAR2 standards: why src/ instead of lib/?

Chuck Hagenbuch wrote:

Quoting Christian Weiske <cweiske@cweiske.de>:

I know I'm probably missing the proper channel for this, but: why does PEAR2 specify src/ instead of lib/ for class files? src/, to me, implies source code - files to be processed (which is discouraged for PEAR2). lib/ implies libraries, which is really what this is. lib/ also matches a lot of existing PHP idioms, as well as ruby and python packages. So I'm strongly considering standardizing on lib/ for Horde, and was wondering if PEAR would consider switching :) or if there was a strong reason for src/ instead.

Because for PEAR packages, the code is code. It's a lib for other people/programs, but for the package itself, it's just code. If the package would need/depend on another lib, this could go into lib/.

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, it should distribute them in lib/ if that's where they're going to be unzipped. In my opinion, of course. :) I'm also not sure that different projects having different directories here would cause any problems, in which case I am more than happy to amicably disagree. I just wanted to make sure I wasn't missing anything, and wouldn't be wreaking havoc. -chuck unzip and go is still a package built by the installer, so you won't be including from src

-josh