1 |
On Wed, Oct 19, 2011 at 7:07 PM, Nilesh Govindarajan |
2 |
<contact@××××××××.com> wrote: |
3 |
> On 10/20/2011 06:57 AM, Canek Peláez Valdés wrote: |
4 |
>> On Wed, Oct 19, 2011 at 6:00 PM, Nilesh Govindarajan |
5 |
>> <contact@××××××××.com> wrote: |
6 |
>>> On Thu 20 Oct 2011 05:30:24 AM IST, Canek Peláez Valdés wrote: |
7 |
>>>> On Wed, Oct 19, 2011 at 1:52 PM, Albert W. Hopkins |
8 |
>>>> <marduk@×××××××××××.org> wrote: |
9 |
>>>>> On Wed, 2011-10-19 at 13:11 -0700, Canek Peláez Valdés wrote: |
10 |
>>>>>> Why don't you try networkmanager-0.9.1.90? It's working great for me |
11 |
>>>>>> in GNOME 3.2.0 |
12 |
>>>>>> |
13 |
>>>>>> Is there something in the live ebuild that you need? |
14 |
>>>>>> |
15 |
>>>>> I can't confirm (never tried it) but I've been told the autounmask |
16 |
>>>>> option in portage will "blindly" unmask even live ebuilds.. which might |
17 |
>>>>> account for people suddenly pulling in a surprising (and potentially |
18 |
>>>>> problematic) amount of live ebuilds. |
19 |
>>>> |
20 |
>>>> I haven't tried the autounmask option from portage, neither. The GNOME |
21 |
>>>> overlay offers a series of files you can link to your |
22 |
>>>> /etc/portage/package.{unmask,keywords,use,use.mask} directories: They |
23 |
>>>> are located in |
24 |
>>>> |
25 |
>>>> ${OVERLAYDIR}/status/portage-configs/ |
26 |
>>>> |
27 |
>>>> I haven't used those either, though. I prefer to unmask/keyword |
28 |
>>>> packages myself. What I do know is that using live ebuilds is |
29 |
>>>> basically flipping a coin; sometimes will work great, sometimes it |
30 |
>>>> will not even compile. |
31 |
>>>> |
32 |
>>>> Right now the only live ebuilds I'm using are: |
33 |
>>>> |
34 |
>>>> gnome-extra/libgda-9999 |
35 |
>>>> media-sound/rhythmbox-9999 |
36 |
>>>> sys-apps/gnome-disk-utility-9999 |
37 |
>>>> gnome-extra/gnome-shell-extensions-weather-9999 |
38 |
>>>> gnome-extra/gnome-shell-extensions-system-monitor-9999 |
39 |
>>>> |
40 |
>>>> Everything else works with the latest non-live ebuilds. |
41 |
>>>> |
42 |
>>>> Regards. |
43 |
>>> |
44 |
>>> Did you just do emerge gnome (assumging that >=gnome-base/gnome-3.0 is |
45 |
>>> in package.unmask)? I'll try doing that again then, till now autounmask |
46 |
>>> was active. |
47 |
>> |
48 |
>> I did emerge =gnome-base/gnome-3.2.0, and unmasked/keyworded by hand |
49 |
>> the necessary packages. But maybe just check that the "**" is not in |
50 |
>> any file on /etc/portage/package.keyworks/* (except perhaps the ones |
51 |
>> I'm using). If there is no "**" keyworkd, no non-live ebuild should be |
52 |
>> installed. |
53 |
>> |
54 |
>> Oh, and also in /etc/portage/package.unmask/*, of course. |
55 |
>> |
56 |
>> Good luck. |
57 |
> |
58 |
> BTW, which overlays did you use? |
59 |
> I tried after reading (translated version of) german guide on the web |
60 |
> these - gnome, keruspe, suka, rubenqba |
61 |
|
62 |
I just have the gnome overlay, but I don't use layman. I just. |
63 |
|
64 |
git clone git://git.overlays.gentoo.org/proj/gnome.git |
65 |
|
66 |
put the resulting gnome dir in my PORTDIR_OVERLAY environment variable |
67 |
in /etc/make.conf, and then |
68 |
|
69 |
emerge -v =gnome-base/gnome-3.2.0 |
70 |
|
71 |
When I want to see if the overlay has updated, I just "git pull" it. |
72 |
Also, I'm on amd64, not ~amd64 (i.e., I'm on stable). The GNOME stack, |
73 |
udev and systemd are the only unstable packages in my system (except |
74 |
for perhaps a couple of other seldom used programs). |
75 |
|
76 |
I'm carrying my laptop around the globe, so NetworkManager has become |
77 |
almost indispensable for me; I haven't touched |
78 |
/etc/wpa_supplicant/wpa_supplicant.conf in months, and I can connect |
79 |
to all kind of networks. |
80 |
|
81 |
Regards. |
82 |
-- |
83 |
Canek Peláez Valdés |
84 |
Posgrado en Ciencia e Ingeniería de la Computación |
85 |
Universidad Nacional Autónoma de México |