| 1 |
On 18/08/2014 19:06, Timur Aydin wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I am using a closed source software package on my 64 bit gentoo linux |
| 5 |
> system. The software package is "beyond compare" by scooter soft. |
| 6 |
> Because of the way this package is built, it needs a specially patched |
| 7 |
> version of glibc. I have patched my existing glibc version (2.18) and |
| 8 |
> have been avoiding updating my glibc since. Now I am wondering whether |
| 9 |
> the latest update of bcompare will work with the latest glibc (2.19). |
| 10 |
> |
| 11 |
> So, if I upgrade to 2.19 and the package doesn't work, how can I go back |
| 12 |
> to the working, patched 2.18? I know that portage issues the most scary |
| 13 |
> warnings when you try to downgrade glibc. So what does the community |
| 14 |
> recommend? |
| 15 |
> |
| 16 |
|
| 17 |
You should be able to downgrade glibc, provided that you haven't built |
| 18 |
and installed any new packages following the transition from glibc-2.18 |
| 19 |
to glibc-2.19. That said, I would suggest that you back up the root |
| 20 |
filesystem as a contingency measure. |
| 21 |
|
| 22 |
Still, why not test bcompare in a chroot? The latest stage3 tarball |
| 23 |
probably includes glibc-2.19 by now. |
| 24 |
|
| 25 |
--Kerin |
Archives