.version
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Jan 28 22:06:49 2011 +0100 (2011-01-28)
changeset 2284 7ede374110e5
parent 1075 61bfa38f2174
child 1565 a32dc48671c3
child 1793 5cd3dd909770
child 1944 3a7ac3dd859d
child 2057 8398f0469d6a
child 2175 bde8f1be2511
child 2296 d18cc3da3879
child 2427 5a725fbda9e0
child 2582 7c5f0c6ddac1
child 2729 adc12224e93c
child 2863 1081af8ee469
child 2954 b005740d1473
child 3029 06cf4f81a5a2
child 3108 f36a98f63749
child 3177 47a7a813b589
child 3236 b83e6d31adba
permissions -rw-r--r--
config: add an option not to remove the destination directory

In certain circumstances, removing the destination/installation directory
is a bad idea. For example, when the build environment is already taking
care of sanitising the build tree, and pre-installs stuff in there, it is
a very bad idea to remove the destination directory.

This happens now in buildroot, as the crostool-NG backend now installs the
toolchain in the common host-tools directory, and pre-install there a few
host-utilities (eg. host-automake and host-gawk).

Provide a config knob to turn on/off the removal of the destination
directory, defaulting to 'y' (previous behavior), and forced to 'n' when
used as a backend.

Reported-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Yann@1409
     1
hg