Originally Posted by Shirik
Unfortunately I currently do the same. This is the only real way to avoid clutter and to ensure a clean install occurs. However, I think it's something that could be argued as a request for an improvement somewhere post-beta to make it a client-side option.
|
I am going to have to speak my mind on this, programmer to programmer.
Could you not provide a "clean install" option?
The option could be enabled by default so to avoid issues. It could even be enabled for each add-on if that was easier. As long as the file is not being used by the operating system or has some sort of permission restriction, other programmer languages I have used have allowed me to replace files if they already exist.
One option would be to allow add-on authors to force a "clean install" if they change the file structure in a release. This could be a flag that the program itself knows about on a given release version of an add-on.
I am trying to whore my ideas out.
