Patches: file edit VS file replace

[emanuele45]

Since #3256 has been merged and we have a nice namespace, I was thinking to advance another proposal: from 2.0 onward, any time during a micro update there is a change in a file in the ElkArte directory, instead of supporting the standard patching, the files are just replaced.
This has two implications:

1. much easier updates (well, once I rewrote the code to create the packages)
2. any addon that modifies one of these files should be presented with a way to interact with them without having to edit.

1 it's relatively easy, 2 may require some more work.

But I think at this point it may be an interesting move.

Opinions?

[Spuds]

Maybe if an addon has to modify a core file we could provide a simple way to flag that activity in the db.
Then when a patch comes out we check that "list" and if a file we are going to replace has been altered by an addon the patch simply says that you need to uninstall addon xyz before you can upgrade ? Or use a file checksum which would also catch any hand editing.

Of course it would be nice to provide such flexibility that an edit is never needed, its just hard to envision all of the tweaks people do.