| 1 |
On 18 August 2014 20:06:51 CEST, Timur Aydin <ta@××××××.org> 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 |
| 12 |
>back |
| 13 |
>to the working, patched 2.18? I know that portage issues the most scary |
| 14 |
> |
| 15 |
>warnings when you try to downgrade glibc. So what does the community |
| 16 |
>recommend? |
| 17 |
|
| 18 |
In cases like that I would do either of the following: |
| 19 |
|
| 20 |
1) Run it inside a VM |
| 21 |
2) run it inside a chroot |
| 22 |
|
| 23 |
That way you can easily keep everything updated except for that application. |
| 24 |
|
| 25 |
-- |
| 26 |
Joost |
| 27 |
|
| 28 |
-- |
| 29 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives