| 1 |
On Mon, Sep 15, 2008 at 11:57 PM, Andreas Prieß <ap@××××××××××.net> wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> I think, if you have a look at the emerge option |
| 5 |
> --with-bdeps < y | n > |
| 6 |
> you should be able to get really, really all possible updates with emerge |
| 7 |
> and without further gimmicks. |
| 8 |
> |
| 9 |
> If it returns "0 packages" to update, try also this |
| 10 |
>> (it takes very long time to finish, requires app-portage/portage-utils) |
| 11 |
>> |
| 12 |
>> # for f in `qlist -IC`; do emerge -puDvNt $f | grep ebuild; done |
| 13 |
>> |
| 14 |
> |
| 15 |
> There should not be any difference if you use the mentioned option to |
| 16 |
> emerge. |
| 17 |
|
| 18 |
|
| 19 |
Unless of course |
| 20 |
1) a package is installed |
| 21 |
2) that package has been upgraded |
| 22 |
3) that package is absent from world |
| 23 |
4) no packages exist in world which that package is a dependant of ( via |
| 24 |
recursive propogation ) |
| 25 |
|
| 26 |
However, imo, such entries should either be injected into world, or removed |
| 27 |
:) |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Kent |
| 32 |
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| |
| 33 |
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}' |
Archives