| 1 |
Apparently, though unproven, at 23:13 on Sunday 12 September 2010, Enrico |
| 2 |
Weigelt did opine thusly: |
| 3 |
|
| 4 |
> Hi folks, |
| 5 |
> |
| 6 |
> |
| 7 |
> I've got a tricky task for automatic update script, which requires |
| 8 |
> some portage magic ... |
| 9 |
> |
| 10 |
> The script has a list of packages which should be updated |
| 11 |
> completely automatically, but *only* if they're pulled in as |
| 12 |
> dependency (beginning from world), and others not in that list |
| 13 |
> should *not* be updated. |
| 14 |
> |
| 15 |
> Is there any easy way to do it ? |
| 16 |
|
| 17 |
man emerge shows a way for the specific case if you are updating world: |
| 18 |
|
| 19 |
--deselect |
| 20 |
|
| 21 |
It basically removes items in the build list that are in world. However if you |
| 22 |
are running |
| 23 |
|
| 24 |
emerge app1 app2 app3 |
| 25 |
|
| 26 |
then the man page implies it won't do what you want. |
| 27 |
|
| 28 |
I don't know when this feature arrived. I run v2.2 and there's been a lot of |
| 29 |
update activity in portage this last week |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
alan dot mckinnon at gmail dot com |
Archives