Re: publicweb RFC
| From: | Greg Beaver | Date: | Wed, 06 Aug 2003 06:38:06 +0000 |
| Subject: | Re: publicweb RFC | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19317@lists.php.net to get a copy of this message | ||
Hi Arnaud,
I agree. I think the installer doesn't delete directories at all currently, but if it ever does, I'm sure a check could be made on whether a directory is empty before deleting it.
Obviously, the user can't change files, which is a problem for .js files and images, but a well-designed project will take this into account and make it easy for the user to copy the files :)
Grge
Limbourg Arnaud wrote:
5. addition of new directories to publicweb and deletion should happen through a new set of commands that perform the upgrade/uninstall automatically to directories. In other words, if a directory is added to the publicweb_dir, the files for existing packages are copied. If a directory is removed, the files are deleted. A few options should allow control over this similar to the --force option for install. pear add-webdir/pear delete-webdir ?I think if the user added files which were not installed by the installer it would be bad manners to remove the directory. The rest of the RCF makes sense. It gives control. Arnaud.