public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Networkmanager-9999 won't compile
Date: Wed, 19 Oct 2011 18:27:18 -0700	[thread overview]
Message-ID: <CADPrc81pXgXaLg=8NoGriHgKumvON09vqgLZwYuz4=M2C68+vQ@mail.gmail.com> (raw)
In-Reply-To: <4E9F7296.2050001@nileshgr.com>

On Wed, Oct 19, 2011 at 6:00 PM, Nilesh Govindarajan
<contact@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
>> <marduk@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.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México



  reply	other threads:[~2011-10-20  1:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19  9:30 [gentoo-user] Networkmanager-9999 won't compile Nilesh Govindarajan
2011-10-19 20:11 ` Canek Peláez Valdés
2011-10-19 20:52   ` Albert W. Hopkins
2011-10-20  0:00     ` Canek Peláez Valdés
2011-10-20  1:00       ` Nilesh Govindarajan
2011-10-20  1:27         ` Canek Peláez Valdés [this message]
2011-10-20  2:07           ` Nilesh Govindarajan
2011-10-20  2:52             ` Canek Peláez Valdés
2011-10-20  3:15             ` Albert W. Hopkins
2011-10-20  1:53   ` Nilesh Govindarajan
2011-10-20  9:04     ` Neil Bothwick
2011-10-20  9:18 ` Jonas de Buhr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADPrc81pXgXaLg=8NoGriHgKumvON09vqgLZwYuz4=M2C68+vQ@mail.gmail.com' \
    --to=caneko@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox