Re: XML_Tree

On Sat, 2005-04-23 at 09:27 +0200, Dave Mertens wrote: > Well helgi, I guess that you're in the same situation as i was with > Crypt_RC4. After a small discussion with Arnaud and Matthew we decided > to split up the version. Within a few weeks Matthew will create a new > packahe called crypt_rc4v2, i guess that what's has to happen woith > xml_tree too. > > On the other hand, the pear installer (or upgrader if you like) can work > in two ways. First, a administrator tells pear exactly what package(s) > to update. The other way is what i call the 'windowsupdate' way. the > pear installer get the current list with packages from the server and > update all packages which have a newer version. > > Developers/companies/administrators who are using the first way, will > (hopefully) always test a newer version of a software package to find > any potential problems. They will notice the BC break and NOT update to > the new (v2) version. I know companies that have put the pear upgradeall > in the crontab, so they can say, we're always running the lastest > version. Most of the time these are also know as hosting partners. And > that brings us to the core of the problem. There are a lot of developers > can cannot force an ISP or hosting provider to run a specific version of > a software package. So the only 'safe' solution to the problems is to > create a new package.. > > I know, as a developer i really dislike this way of development. Except > for the packages that come with PHP, i haven't installed any other > packages globally on my machine. For each website i simply create a > directory 'pear' and put all the pear packages that I need for that > website in there. This all under the motto 'if it ain't broken, don't > fix it'.. ;-) Yes not everyone are smart enough to do that ;-) But well it seems we'll either have to make v1 or v2 people suffer and we kind will probably go into making v1 people suffer since they are in the stone age yet, at least everyone that took apart in the discussion about this earlier today agreed on releasing XML_Tree v2 and skip releasing XML_Tree2 and just go straight to XML_Tree3 if there will ever be a v3. Tho we will probably as I said discuss this at the conference in amsterdam. - Helgi