Re: PEAR2 package naming standards (namespace usage)

Hi, Michael Gauthier wrote:

Once again I see the svn:externals handwaving here. Can you please

describe a

real world scenario where svn:externals will be useful for working

with PEAR

packages? Thanks in advance.

If someone is not a PEAR developer, the current PEAR development process is a barrier. I'd argue most PHP developers are not accustomed to a 'build' or 'package' step during development. Most developers run code directly from their development branch.

You mean they checkout directly to DocumentRoot and use the same config file for both development and production servers? If they aren't then they still have to perform some 'build' and/or 'package' step even if said step consists of copying some files somewhere.

The PEAR approach does have its advantages but it _is_ more complicated and _is_ harder for new developers to work with. As an example, at silverorange we used PEAR::Date for years before we even used version control or PEAR. It was always a hassle to provide patches and to patch our version. For this reason it wasn't until many years later that we started using other PEAR packages.

You quoted my question but didn't answer it. I was asking for a real word scenario where svn:externals would be useful for working with PEAR packages. Can you show how svn:externals would be useful to provide patches or to patch your version of PEAR::Date especially if you weren't using version control back then?