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 Index: binutils-2.19.51.0.5/ld/ld.texinfo
2 ===================================================================
4 diff -durN binutils-2.20.1.orig/ld/ld.texinfo binutils-2.20.1/ld/ld.texinfo
5 --- binutils-2.20.1.orig/ld/ld.texinfo 2009-07-06 15:48:51.000000000 +0200
6 +++ binutils-2.20.1/ld/ld.texinfo 2010-08-17 19:32:16.000000000 +0200
8 systems may not understand them. If you specify
9 @option{--enable-new-dtags}, the dynamic tags will be created as needed.
10 If you specify @option{--disable-new-dtags}, no new dynamic tags will be
11 -created. By default, the new dynamic tags are not created. Note that
12 -those options are only available for ELF systems.
13 +created. On Gentoo, by default, the new dynamic tags are created (this
14 +differs from upstream behaviour). Note that those options are only
15 +available for ELF systems.
17 @kindex --hash-size=@var{number}
18 @item --hash-size=@var{number}