Re: Image_Text mess in CVS

Hi! Tobias Schlitt wrote:

Just maintain a second pear install tree for testing:

alias peartest="pear -f ~/.peartestrc" T=~/peartest mkdir $T peartest -d bin_dir=$T/bin -d doc_dir=$T/docs -d ext_dir=$T/libexec \

        -d php_dir=$T/lib/php -d data_dir=$T/data -d test_dir=$T/tests

Now you can do "peartest install package.xml" etc.

That would definitly be a clean solution. But I guess it's unmanagable in PEAR. CVS is a repository for deleopement. And package.xml is mostly touched only short befor a release. So, I guess in most cases, the package.xml residing in CVS is not valid for the code. I would allways have to check package.xml before I can do that. And that's quite more uncomfortable than handling ln's.

But you'll need to install only the packages *you* are developing from CVS. All other packages can be installed to 'peartest' from releases. And you probably can manage adding the files to the package.xml file after you add them to your package. ;]