| 1 |
Holly Bostick wrote: |
| 2 |
|
| 3 |
>>So, any thoughts on why "emerge --newuse" doesn't want to rebuild |
| 4 |
>>apache? |
| 5 |
>> |
| 6 |
>> |
| 7 |
> |
| 8 |
>Well, assuming it's not a bug (what version of Portage are you using?) |
| 9 |
>then is it possible that apache is neither in your world file, |
| 10 |
> |
| 11 |
> |
| 12 |
I'm on portage 2.0.51.22-r3. This is a very new system - as part of the |
| 13 |
install sequence portage was of course updated, so it was some earlier |
| 14 |
portage version a week ago. |
| 15 |
|
| 16 |
Seems a truism, but you're right. apache isn't in my world file. |
| 17 |
somehow. And adding it to my world file does work around the symptom I |
| 18 |
describe. |
| 19 |
|
| 20 |
This begs the question of why it isn't there, considering it is |
| 21 |
installed. I must wonder, what else that I've installed has somehow not |
| 22 |
been added to the world file. Perhaps I'm exposing my ignorance, but is |
| 23 |
the world file not supposed to have everything that is installed and not |
| 24 |
in the base system definition? Under what circumstances (other than |
| 25 |
failed/aborted emerge, which didn't happen) could something fail to go |
| 26 |
into world? |
| 27 |
|
| 28 |
Thanks, |
| 29 |
|
| 30 |
glen |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-user@g.o mailing list |
Archives