| 1 |
On 22/05/2015 12:44, Mick wrote: |
| 2 |
> On Friday 22 May 2015 09:38:46 Neil Bothwick wrote: |
| 3 |
>> On Fri, 22 May 2015 02:53:17 -0500, Dale wrote: |
| 4 |
>>>> So I'm the 3rd one in row to state that I haven't had any deleterious |
| 5 |
>>>> effects that I noticed. |
| 6 |
>> |
| 7 |
>> Make that 4. |
| 8 |
>> |
| 9 |
>>> When I first emerge a new kernel, I run make mrproper to get a good |
| 10 |
>>> clean start. |
| 11 |
>> |
| 12 |
>> There's no point in that. When you have just emerged the sources, there is |
| 13 |
>> nothing for mrproper to remove. |
| 14 |
> |
| 15 |
> |
| 16 |
> So, coming back to the OP, is it advisable to ignore this message: |
| 17 |
|
| 18 |
|
| 19 |
No. It's in the ebuild and we assume the ebuild writer had a reason for |
| 20 |
putting it there. The usual reason is that upstream has said their code |
| 21 |
requires an option to be set. |
| 22 |
|
| 23 |
Where would you have gotten the idea that ignoring it is good advice? |
| 24 |
|
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
> |
| 29 |
> * Messages for package www-client/chromium-43.0.2357.65: |
| 30 |
> [27/1984] |
| 31 |
> |
| 32 |
> * USER_NS is required for sandbox to work |
| 33 |
> * Please check to make sure these options are set correctly. |
| 34 |
> * Failure to do so may cause unexpected problems. |
| 35 |
> |
| 36 |
> which doesn't even advise where to find USER_NS, or will chromium no longer |
| 37 |
> work as it did in the past? |
| 38 |
> |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
Alan McKinnon |
| 43 |
alan.mckinnon@×××××.com |
Archives