Re: PEAR2 package naming standards (namespace usage)
| From: | Joshua Eichorn | Date: | Thu, 28 Aug 2008 16:27:23 +0000 |
| Subject: | Re: PEAR2 package naming standards (namespace usage) | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-50675@lists.php.net to get a copy of this message | ||
Alexey Borzov wrote:
Hi, Joshua Eichorn wrote:-joshSVN is a 3rd party program and shouldn't be a concern in the design: SVN is how we are managing code in pear2, and hopefully soon in all of PHP. It and tools with similar rules like git is how the open source world manages code.My concern was not with SVN, but with svn:externals specifically, and your propaganda-like answer "this is how The Open Source World Manages Code" doesn't even try to address that concern! svn:externals is essentially a tool for managing external dependencies. Then again we already have a tool for managing external dependencies and it is called "PEAR the Installer". So the question is: why are we trying to get rid of one thing that Works in PEAR1 and switch to some other things? Here I mean the idea about unzip-and-run vs. installable packages and now svn:externals for dependencies handling. Is this how the open source world manages code? Point taken, I would like to allow all 3 methods.