On Wed, Oct 19, 2011 at 7:07 PM, Nilesh Govindarajan
<cont...@nileshgr.com> wrote:
> On 10/20/2011 06:57 AM, Canek Peláez Valdés wrote:
>> On Wed, Oct 19, 2011 at 6:00 PM, Nilesh Govindarajan
>> <cont...@nileshgr.com> wrote:
>>> 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.
>>
>> I did emerge =gnome-base/gnome-3.2.0, and unmasked/keyworded by hand
>> the necessary packages. But maybe just check that the "**" is not in
>> any file on /etc/portage/package.keyworks/* (except perhaps the ones
>> I'm using). If there is no "**" keyworkd, no non-live ebuild should be
>> installed.
>>
>> Oh, and also in /etc/portage/package.unmask/*, of course.
>>
>> Good luck.
>
> BTW, which overlays did you use?
> I tried after reading (translated version of) german guide on the web
> these - gnome, keruspe, suka, rubenqbaI just have the gnome overlay, but I don't use layman. I just. git clone git://git.overlays.gentoo.org/proj/gnome.git put the resulting gnome dir in my PORTDIR_OVERLAY environment variable in /etc/make.conf, and then emerge -v =gnome-base/gnome-3.2.0 When I want to see if the overlay has updated, I just "git pull" it. Also, I'm on amd64, not ~amd64 (i.e., I'm on stable). The GNOME stack, udev and systemd are the only unstable packages in my system (except for perhaps a couple of other seldom used programs). I'm carrying my laptop around the globe, so NetworkManager has become almost indispensable for me; I haven't touched /etc/wpa_supplicant/wpa_supplicant.conf in months, and I can connect to all kind of networks. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
