| 1 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 2 |
>> User installs foo-1.1-r1 |
| 3 |
>> Developer makes foo-1.1-r2 |
| 4 |
>> foo-1.1* is removed from the tree |
| 5 |
>> User syncs |
| 6 |
>> |
| 7 |
>> In fact, the result is completely the same |
| 8 |
|
| 9 |
You completely ignored this essential point: |
| 10 |
The result is completely the same, and you are |
| 11 |
just arguing with a strawman. |
| 12 |
|
| 13 |
But, OK, so I will use your strawman to prove |
| 14 |
how static deps are broken: |
| 15 |
|
| 16 |
>> What is *actually* broken here is that the user |
| 17 |
>> has installed a package which is not maintained |
| 18 |
>> anymore: *This* is what needs to be fixed. |
| 19 |
> |
| 20 |
> Uhm. That works just fine... |
| 21 |
|
| 22 |
Not at all: |
| 23 |
|
| 24 |
1. Some package depending on foo/bar is removed, |
| 25 |
but the user keeps it, since deps are stored in /var/db. |
| 26 |
|
| 27 |
2. foo/bar is split into foo/bar-A foo/bar-B |
| 28 |
for whatever reasons. Of course, all maintained ebuilds |
| 29 |
fix the dependency, and let us assume they are even |
| 30 |
revbumped. |
| 31 |
|
| 32 |
3. The orphaned package of course still depends on |
| 33 |
installed foo/bar, causing all sort of blockers. |
| 34 |
|
| 35 |
4. The user has no way for fixing the issue than |
| 36 |
in modifying /var/db manually. He cannot even put |
| 37 |
an ebuild into his overlay and only modify this |
| 38 |
ebuild and the metadata, because the PM dumbly |
| 39 |
insists on using only the (broken and outdated |
| 40 |
since ages) information in /var/db |
| 41 |
|
| 42 |
> I don't think you understand how this works: |
| 43 |
|
| 44 |
Quite the opposite: I see that it fixes many issues. |
| 45 |
It has also some issues with orphaned packages, |
| 46 |
but *every* approach will have issues with orphaned |
| 47 |
packages. |
Archives