Description: ------------ When loading an existing package.xml file, I cannot change the autodetected baseinstalldir. There should be an option to completely not use baseinstalldir. Test script: --------------- $ pfm . PEAR Package File Manager Command Line Tool Enter the base install directory 1) HTML/Template Please choose an option: 1 PEAR Package File Manager Command Line Tool 1. Package name [HTML_Template_PHPLIB] 2. Channel/URI [Channel: pear.php.net] 3. Summary [preg_* based template system.] 4. Description [The popular Template system from PHPL...] 5. Maintainers 6. Version [Release: 1.3.3 API: 1.3.3] 7. Stability [Release: stable API: stable] 8. License [LGPL] 9. Notes [- method to retrieve last error] 10. Dependencies 11. Tasks 12. Regenerate contents 13. Echo package file to stdout 14. Save & Quit 15. Quit without saving (ctrl-c) Please choose an option from the menu: 15

This one's a bit tricky. For one thing, PEAR_PackageFileManager throws a PEAR_Error when you don't specify or leave the baseinstalldir blank. The other thing is that different files have different baseinstalldirs. When editing an existing package file, I leave the existing file attributes as they are (by leaving clearcontents set to false). I'll add the ability to choose an existing baseinstalldir or type your own, but currently this will only affect new files. I plan to also add the ability to edit each individual file's attributes, in which case pfm needs to be able to remember which files have been manually changed between saves. When this ability is added then you can change the baseinstalldir on a per file basis.

Ok.

Most commonly for me, I find I renamed dirs and need to change the baseinstalldir to "/". I've added fixes to achieve that - do that help/make this closable?