On Thu 20 Oct 2011 05:30:24 AM IST, Canek Peláez Valdés wrote:
> On Wed, Oct 19, 2011 at 1:52 PM, Albert W. Hopkins
> <mar...@letterboxes.org> wrote:
>> On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote:
>>> Why don't you try networkmanager-0.9.1.90? It's working great for me
>>> in GNOME 3.2.0
>>>
>>> Is there something in the live ebuild that you need?
>>>
>> I can't confirm (never tried it) but I've been told the autounmask
>> option in portage will "blindly" unmask even live ebuilds.. which might
>> account for people suddenly pulling in a surprising (and potentially
>> problematic) amount of live ebuilds.
>
> I haven't tried the autounmask option from portage, neither. The GNOME
> overlay offers a series of files you can link to your
> /etc/portage/package.{unmask,keywords,use,use.mask} directories: They
> are located in
>
> ${OVERLAYDIR}/status/portage-configs/
>
> I haven't used those either, though. I prefer to unmask/keyword
> packages myself. What I do know is that using live ebuilds is
> basically flipping a coin; sometimes will work great, sometimes it
> will not even compile.
>
> Right now the only live ebuilds I'm using are:
>
> gnome-extra/libgda-9999
> media-sound/rhythmbox-9999
> sys-apps/gnome-disk-utility-9999
> gnome-extra/gnome-shell-extensions-weather-9999
> gnome-extra/gnome-shell-extensions-system-monitor-9999
>
> Everything else works with the latest non-live ebuilds.
>
> Regards.

Did you just do emerge gnome (assumging that >=gnome-base/gnome-3.0 is 
in package.unmask)? I'll try doing that again then, till now autounmask 
was active.

-- 
Nilesh Govindarajan
http://nileshgr.com

Reply via email to