| 1 |
Andreas K. Huettel posted on Sun, 24 Jul 2016 00:04:53 +0200 as excerpted: |
| 2 |
|
| 3 |
> 1) If a package only ever had one slot, it cannot ever have two versions |
| 4 |
> installed at the same time. That guarantee (of only ever one slot) can |
| 5 |
> be given for the portage tree (sic). Obviously it doesn't work for |
| 6 |
> overlays, |
| 7 |
> but there are many things we don't care about for overlays. [A] |
| 8 |
|
| 9 |
This is incorrect. It arguably /might/ be correct if systems were |
| 10 |
guaranteed never to crash in the qmerge or old-version unmerge phases, |
| 11 |
but... the package manager must be able to deal with and recover from |
| 12 |
such crashes, and portage has done so for well over a decade, at least. |
| 13 |
|
| 14 |
(When I became a gentooer in 2004 I had faulty hardware, and the system |
| 15 |
would regularly crash during merges, sometimes repeatedly. When I |
| 16 |
rebooted, all I had to do was restart the merge, and portage could pick |
| 17 |
up the pieces and deal with it, even back then.) |
| 18 |
|
| 19 |
> 2) If a package manager leaves two versions of a non-slotted package |
| 20 |
> "installed" somehow, that package manager is fundamentally broken and |
| 21 |
> its author should forever refrain from specifying anything. It's not our |
| 22 |
> job to work around Paludis failure modes. [B] |
| 23 |
|
| 24 |
Not if it's the hardware that's broken, not the PM. A good PM must be |
| 25 |
able to recover from the crash, and sort things out from it on a second, |
| 26 |
or third or tenth, attempt to actually get the upgrade done, this time |
| 27 |
/without/ crashing part way thru. |
| 28 |
|
| 29 |
And broken ebuilds that can't deal with the situation don't help matters |
| 30 |
at all. =:^( |
| 31 |
|
| 32 |
-- |
| 33 |
Duncan - List replies preferred. No HTML msgs. |
| 34 |
"Every nonfree program has a lord, a master -- |
| 35 |
and if you use the program, he is your master." Richard Stallman |
Archives