PEAR2 standards: why src/ instead of lib/?

From: Date: Mon, 03 Mar 2008 05:01:45 +0000
Subject: PEAR2 standards: why src/ instead of lib/?
Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-49236@lists.php.net to get a copy of this message
Hi PEAR folks- 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. -chuck

« previous php.pear.dev (#49236) next »