| 1 |
On Mon, 23 Jan 2006 08:25:12 -0600 |
| 2 |
Mikey <mikey@×××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Monday 23 January 2006 04:56, Patrick Börjesson spammed: |
| 5 |
> |
| 6 |
> > The problem with your reasoning is that portage only reports the |
| 7 |
> > "highest" upgrade (from it's point of view). So if you have package |
| 8 |
> > A-1.0 installed and two possible upgrades, say A-1.0-s1 and A-1.1, |
| 9 |
> > then portage will chose the "highest" of the two. So the output |
| 10 |
> > from that |
| 11 |
> > |
| 12 |
> > command would be: |
| 13 |
> > | These are the packages that I would merge, in reverse order: |
| 14 |
> > | |
| 15 |
> > | Calculating world dependencies ...done! |
| 16 |
> > | [ebuild U ] the-cat/A-1.1 [1.0] ...... |
| 17 |
> > |
| 18 |
> > It will not output the following: |
| 19 |
> > | These are the packages that I would merge, in reverse order: |
| 20 |
> > | |
| 21 |
> > | Calculating world dependencies ...done! |
| 22 |
> > | [ebuild U ] the-cat/A-1.0-s1 [1.0] ...... |
| 23 |
> > |
| 24 |
> > So you _will_ miss upgrades if you only filter the output of emerge |
| 25 |
> > in your solution and expect to get all security related upgrades |
| 26 |
> > relating to the package you're using. |
| 27 |
> |
| 28 |
> That is _exactly_ how it is intended to work. "Normal" users will |
| 29 |
> get A-1.1 when they run emerge -u. Users with a need for stability |
| 30 |
> will only see A-1.0-s1, and only if it is available for A-1.0. |
| 31 |
|
| 32 |
And for that you have to hack the resolver so it only sees your -sX |
| 33 |
updates. |
| 34 |
|
| 35 |
Marius |
| 36 |
|
| 37 |
-- |
| 38 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 39 |
|
| 40 |
In the beginning, there was nothing. And God said, 'Let there be |
| 41 |
Light.' And there was still nothing, but you could see a bit better. |
Archives