| 1 |
Hi all, |
| 2 |
|
| 3 |
bug 490350 [1] brought me to think about the way rebuilds are currently |
| 4 |
handled/can be influenced. |
| 5 |
|
| 6 |
When a new version of some package is about to be installed in the same |
| 7 |
slot as the installed version and this new version has a different sub |
| 8 |
slot then I see 3 different things one can do: |
| 9 |
|
| 10 |
a) Install the new version and rebuild everything that has a slot |
| 11 |
operator dep on it. (The current default.) |
| 12 |
|
| 13 |
b) Skip the update and skip all rebuilds. (You might be able to do this |
| 14 |
using --exclude) |
| 15 |
|
| 16 |
c) Perform the update, don't rebuild anything (rely on preserved-libs, |
| 17 |
revdep-rebuild). This is --ignore-built-slot-operator-deps=y. |
| 18 |
|
| 19 |
Note that a) and b) are safe things to do, while c) has the potential to |
| 20 |
break stuff. |
| 21 |
|
| 22 |
I'd expect that what the user wants, generally depends on the context. |
| 23 |
For "-uDN world" I'd expect a), but for "emerge foo" I'd expect b) |
| 24 |
unless foo is the update I was talking about. In the latter case I'd |
| 25 |
expect a) or c). |
| 26 |
|
| 27 |
Before I continue, I'd like to know if you agree with my analyses. Am I |
| 28 |
missing something? |
| 29 |
|
| 30 |
|
| 31 |
Sebastian |
| 32 |
|
| 33 |
|
| 34 |
[1] Bug 490350 - sys-apps/portage: Extended user interface of |
| 35 |
--ignore-built-slot-operator-deps=y |
| 36 |
URL: https://bugs.gentoo.org/show_bug.cgi?id=490350 |
Archives