scripts/addToolsVersion: properly handle .in vs. .in.2
While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).
Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.
So, for each tool, we need to explicitly know what file to munge.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
1 do not bother running ldconfig on DESTDIR. it wants to write the temp cache
2 file outside of the chroot. doesnt matter anyways as we wont use the cache
3 results (portage will rebuild cache), so running ldconfig is simply a waste
6 diff -durN glibc-2.12.1.orig/Makefile glibc-2.12.1/Makefile
7 --- glibc-2.12.1.orig/Makefile 2009-04-23 20:23:03.000000000 +0200
8 +++ glibc-2.12.1/Makefile 2009-11-13 00:49:49.000000000 +0100
10 rm -f $(symbolic-link-list)
13 +dont-bother-with-destdir:
14 -test ! -x $(common-objpfx)elf/ldconfig || LC_ALL=C LANGUAGE=C \
15 $(common-objpfx)elf/ldconfig $(addprefix -r ,$(install_root)) \