Re: PEAR2 package naming standards (namespace usage)

On Mon, 2008-09-01 at 19:59 +0400, Alexey Borzov wrote: > > This naming schema provides a simple blueprint that can be adopted by > > anyone wishing to package their PHP code without having to invent some > > sorta of pseudo-categorization schema like PEAR1 while also addressing > > the concerns of those of us who use tools like Subversion and Git - > > including their svn:externals and git:submodules features - on a daily > > basis in their job. > > 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. 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. Mike