Re: CVS is your friend

AS an addition, many IDE let you execute external commands and bind a shortcut to them. Let's say you work on LiveUser, you just need to create a liveuser.sh (or .bat) with pear install --force /path/to/liveuser/package.xml In the IDE, you bind F7 to run this script. In one keystroke you can have an easy development :) Arnaud.

I disagree - it's so incredibly simple to install and then uninstall, which is much less simple than downloading, making sure it is in the include path, including it, and then possibly deleting it if you don't need it. I always install packages to test them. Basically, I have another window open where I have once typed: "pear install --force package.xml" in the directory that contains the package.xml. Then, when I make changes, I hit up-arrow <enter> in that window. It's not exactly difficult :). Plus, I can be sure that it will work when people pear install it - something that you can't be sure of if you forget to test this on a release. Then, if I want to use another set, I just pear uninstall Packagename. This is the primary advantage of PEAR over CVS - you can use CVS to keep track of the "source" but you can create a workable snapshot with the package.xml and install/upgrade features of PEAR - something CVS will never match (and is not intended to match). For those who operate in a single-window installation, creation of a shell script that contains something like: #!/bin/sh pear install --force $1/package.xml would work nicely. devinstall /path/to/package Greg