public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Advice needed regarding udisks
Date: Sat, 24 Aug 2013 15:14:33 +0200	[thread overview]
Message-ID: <20130824151433.783f80df@marcec> (raw)
In-Reply-To: <CAN0CFw1Vk-SMzSc2p9r2k34+yNr3qztA+6+NskCwHe4TnoMqCw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

Am Sat, 24 Aug 2013 05:43:39 -0700
schrieb Grant <emailgrant@gmail.com>:

[...]
> >> If I keyword gvfs I get into trouble because gobject-introspection
> >> wants <dev-libs/glib-2.33 and gvfs wants >=dev-libs/glib-2.36.
> >>
> >
> > So?
> >
> > Obviously I meant to say 'keyword gvfs *and it's dependencies* from ~arch if
> > you want to use USE="udev udisks"'
> 
> The above glib dependencies are circular.  There is no way to satisfy them both.
> 
> - Grant

Samuli means this:

$ grep dev-libs/glib /usr/portage/dev-libs/gobject-introspection/*.ebuild 
/usr/portage/dev-libs/gobject-introspection/gobject-introspection-1.32.1.ebuild:	>=dev-libs/glib-2.31.22:2
/usr/portage/dev-libs/gobject-introspection/gobject-introspection-1.32.1.ebuild:	<dev-libs/glib-2.33:2
/usr/portage/dev-libs/gobject-introspection/gobject-introspection-1.34.2-r1.ebuild:	>=dev-libs/glib-2.34.1:2
/usr/portage/dev-libs/gobject-introspection/gobject-introspection-1.36.0.ebuild:	>=dev-libs/glib-2.36:2

So you need >=gobject-introspection-1.34.2 to satisfy the dependencies.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-08-24 13:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 13:09 [gentoo-user] Advice needed regarding udisks Grant
2013-08-17  7:57 ` [gentoo-user] " Grant
2013-08-17  8:33   ` Alan McKinnon
2013-08-17 18:03     ` Grant
2013-08-17 18:15       ` Canek Peláez Valdés
2013-08-17 19:00         ` Grant
2013-08-17 19:20           ` Canek Peláez Valdés
2013-08-17 19:28           ` Alan McKinnon
2013-08-18  7:33             ` Grant
2013-08-18  9:21               ` Alan McKinnon
2013-08-18  9:50                 ` Grant
2013-08-18 17:46                   ` Jonathan Callen
2013-08-19  7:17                     ` Grant
2013-08-19  7:25                       ` Alan McKinnon
2013-08-19  8:25                         ` Grant
2013-08-19  9:05                           ` Alan McKinnon
2013-08-19  9:43                             ` Grant
2013-08-19  9:49                               ` Alan McKinnon
2013-08-19  7:28                       ` Canek Peláez Valdés
2013-08-23  5:48             ` Grant
2013-08-20  5:40           ` Samuli Suominen
2013-08-20  6:21             ` Grant
2013-08-23 15:15               ` Samuli Suominen
2013-08-24  5:39                 ` Grant
2013-08-24 11:20                   ` Samuli Suominen
2013-08-24 12:43                     ` Grant
2013-08-24 13:14                       ` Marc Joliet [this message]
2013-08-24 14:44                         ` Grant
2013-08-17 18:22       ` Alan McKinnon

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=20130824151433.783f80df@marcec \
    --to=marcec@gmx.de \
    --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