Change the "update" target so it becomes more useful (and less dangerous!).

Here is a summary of the changed behaviour:

 * A "make update" will no longer clean the subtree before running.

 * If called a second time, it will resume package installation, in
   case a previous "make update" was interrupted for some reason.
   (just make sure you don't call "make clean" in between ;-)

 * Unless "NOCLEAN" is set, "make update" will clean up the subtree
   after successfully updating _all_ packages (to avoid a dirty directory
   structure for future makes).

 * A "clean-update" target has been introduced to clean up the subtree
   that gets updated.  This should be used prior to an initial "make
   update" if you suspect that one of the packages that get updated may
   be dirty.

XXX: this still does not automatically check for or update any obsolete
     ´upstream' packages (e.g., if gtk depends on glib, a "make update"
     in the gtk directory won't automatically update glib, you have to
     do it the other way round).

0 files changed, 0 insertions, 0 deletions