| 1 |
On Mon, 2 Nov 2009 13:25:08 +0000, Neil Bothwick <neil@××××××××××.uk> |
| 2 |
wrote: |
| 3 |
> On Mon, 02 Nov 2009 13:58:03 +0100, Jesús Guerrero wrote: |
| 4 |
> |
| 5 |
>> @preserved-rebuild never worked for me, maybe it's just that it doesn't |
| 6 |
>> like ~arch. I am just too lazy to work on how to fix a thing when |
| 7 |
>> there's an alternative that always worked reliably, revdep-rebuild. |
| 8 |
> |
| 9 |
> If it didn't work on ~arch, how would it ever make it into arch? |
| 10 |
> |
| 11 |
I am not the one to answer that, all I can say is that the few times I've |
| 12 |
tried it, it kept rebuilding the same packages again, and again, and again |
| 13 |
ad infinitum, as said, I didn't even bother to find what the problem was, |
| 14 |
because I have a working alternative. Sure it could be better, but that |
| 15 |
hasn't been the case for me with @preserved-rebuild. |
| 16 |
|
| 17 |
I've seen people reporting the same problems in the forums, so I am fairly |
| 18 |
sure that's a common problem and not just exclusive to my installations. |
| 19 |
|
| 20 |
> The trouble with revdep-rebuild is that you have to break your system |
| 21 |
and |
| 22 |
> then fix it. Most of the time this is trivial, but updates like |
| 23 |
expat-2.0 |
| 24 |
> showed the usefulness of being able to recompile the packages before |
| 25 |
they |
| 26 |
> were broken. |
| 27 |
|
| 28 |
I can't understand that. You CAN'T recompile your packages against the new |
| 29 |
ABI's until the new ABI is in your system, and hence your system is already |
| 30 |
broken. There's no preemptive measure against this. Both methods fix the |
| 31 |
system *after* it's broken. |
| 32 |
|
| 33 |
-- |
| 34 |
Jesús Guerrero |
Archives