| 1 |
> Anyway, the portage-2.1.2 tracker bug [1] shows you the |
| 2 |
> differences between |
| 3 |
> portage-2.1.1 and the latest 2.1.2 prerelease. Also a comment |
| 4 |
> from zmedico |
| 5 |
> (the portage dev who is providing us with all of these new |
| 6 |
> features and |
| 7 |
> fixes) [2] clearly shows that the change is intended. |
| 8 |
|
| 9 |
Well, if it's intended, then that's all I need to know... :) |
| 10 |
|
| 11 |
> I believe that should answer your questions. You, however, |
| 12 |
> haven't answered |
| 13 |
> mine. What did you think it should do with --deep without --update? |
| 14 |
|
| 15 |
I'm no expert by any stretch, I just noticed that it was acting different |
| 16 |
and as illustrated, I could prove it. Perhaps I misunderstood what --deep |
| 17 |
was for. I guess I thought it was the package and any dependencies that |
| 18 |
NEEDED upgrade for the package to work. Now it feels like it just pulls in |
| 19 |
the other dependencies just because that's what they are. Again, I could be |
| 20 |
wrong. I just noticed more stuff being shown than usual, that's all. |
| 21 |
|
| 22 |
DÆVID |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-user@g.o mailing list |
Archives