Currently ezpublish-legacy-installer composer plugin installs updates in a temp directory and then copies contents of this directory over previous installation. This is to avoid destructive updates as eZ Publish legacy has extensions and settings at the same level as the kernel and libs.

However this has several drawbacks:

• If on a development branch (e.g. dev-master), Composer will always do a full clone instead of a simple pull.
• If on a development branch (e.g. dev-master) and one wants to switch to a release (e.g. 2013.09.0), .git/ folder is not removed as it should and a git status will thus show a lot of pending changes.