| 1 |
On 9/18/09, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Fri, 18 Sep 2009 12:35:39 +0300, Arttu V. wrote: |
| 3 |
> |
| 4 |
>> eny interactivity (e.g., in make.conf): |
| 5 |
>> |
| 6 |
>> ACCEPT_PROPERTIES="-interactive" |
| 7 |
>> |
| 8 |
>> Then try to emerge something interactive: |
| 9 |
> |
| 10 |
> I just tried that, and instead of skipping the upgrades, it wanted to |
| 11 |
> download several packages to a much older version :( |
| 12 |
|
| 13 |
O.o |
| 14 |
|
| 15 |
Care to share some of the packages causing this? Maybe some packages |
| 16 |
have interactivity marked only in their later versions, and others |
| 17 |
have it in their earlier ones? |
| 18 |
|
| 19 |
As the feature is not advertised on the portage man-page it could also |
| 20 |
be that it is still exceptionally buggy or non-functional somehow (but |
| 21 |
the bug was closed ...) ... and also, maybe there is another way to do |
| 22 |
this? This was the first one I found. |
| 23 |
|
| 24 |
>> Naturally, I'm running 2.2rc-series portage, so 2.1 might not have it. |
| 25 |
> |
| 26 |
> I do, this is a ~amd64 system. |
| 27 |
|
| 28 |
Ok, the box I tried that on was a mostly stable amd64, with only some |
| 29 |
end-user programs and libs (like mozilla-firefox and xulrunner) on |
| 30 |
testing. And naturally portage-2.2rc40, as you couldn't get kde4 |
| 31 |
without it the other year. |
| 32 |
|
| 33 |
-- |
| 34 |
Arttu V. |
Archives