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

Hello Chuck, > 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/. To make it short, we never discussed lib/ since it didn't seem appropriate to anyone of us. -- Regards/Mit freundlichen Grüßen Christian Weiske

Attachment: [application/pgp-signature] signature.asc