Re: Not include mpfr in iso?

Hello Gilles,


>>> So /bin/bash should be the only different file that matter when building
>>> with mpfr-2.4.2 or with 3.0.1-rc1. Hard to know if that matter really.
>>>
>>> Anyway, I think I could remove libmpfr from installed files list.
>>
>> Agreed.
>>
>> Speaking of bash, there's version 4.2 which we may want to include.
>>
>
> Yes. I was a bit frighten by the growing number of patches accumulated since
> 4.2 release.
> There is already 8 patches in half a month for 4.2 when there was only 10
> for 13 month for 4.1

Yes, same happened for 4.1, several patches in a relatively short time 
and then months without changes.


 > I checked and only /bin/bash, libhistory and libreadline are
 > different when upgrading from readline-6.1 to 6.2


OK, so if we put those in the same upgrade as readline we should be safe.


FWIW, below result from
  cd / && find ${EXEC_PATH} -type f -exec scanelf -qRn {} \; | grep readline


libreadline.so.6,libhistory.so.6,libncursesw.so.5,libdl.so.2,libc.so.6 
/bin/bash
libsqlite3.so.0,libreadline.so.6,libncursesw.so.5,libdl.so.2,libpthread.so.0,libc.so.6 
  /usr/bin/sqlite3
libz.so.1,libreadline.so.6,libc.so.6  /usr/bin/gpg
libz.so.1,libreadline.so.6,libc.so.6  /usr/bin/gpgv
libreadline.so.6,libncursesw.so.5,libc.so.6  /usr/bin/bc
libreadline.so.6,libncursesw.so.5,libpython2.5.so.1.0,libpthread.so.0,libc.so.6 
  /usr/lib/python2.5/lib-dynload/readline.so
libncursesw.so.5,libc.so.6  /usr/lib/libreadline.so.6.2



Olaf

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar