There’s one really big drawback to the CQ/CRX package manager…
Imagine you have a application code package with a filter of “/apps/myApp”, which has been built from a recently updated SVN working copy. You want to update your local CRX repository, but you also have current development under way which will be overwritten by the package. Well, in most cases you can remember to make a backup package singling out only your local changes, build that package, install the full code refresh from SVN, and then install your backup package immediately afterward, effectively overlaying your changes/additions on top of an updated code-base. This works, but what if for some reason you forget to back up your local changes in this manner? Once a full package has been installed, there’s no way to go back, right?