public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Something is pulling in gnome-base
Date: Wed, 11 Dec 2013 18:39:59 +0200	[thread overview]
Message-ID: <52A8955F.6090202@gmail.com> (raw)
In-Reply-To: <201312111629.44251.michaelkintzios@gmail.com>

On 11/12/2013 18:29, Mick wrote:
> On Wednesday 11 Dec 2013 10:58:19 Peter Humphrey wrote:
>> On Tuesday 10 Dec 2013 23:49:06 Mick wrote:
>>> I seem to have two packages from gnome:
>>>
>>> # emerge --depclean -v -a app-admin/system-config-printer-gnome
>>>
>>> Calculating dependencies... done!
>>>
>>>   app-admin/system-config-printer-gnome-1.4.3 pulled in by:
>>>     kde-base/print-manager-4.10.5 requires
>>>     app-admin/system-config-printer-
>>>
>>> gnome
>>>
>>> # emerge --depclean -v -a gnome-base/gnome-common
>>>
>>> Calculating dependencies... done!
>>>
>>>   gnome-base/gnome-common-3.7.4 pulled in by:
>>>     dev-python/pygobject-3.8.3 requires gnome-base/gnome-common
>>>
>>> Not sure why they are being pulled in as dependencies ... ?
>>
>> Further to what Alan said, I don't even have print-manager installed here.
>> I checked what would be pulled in if I did install it and found 10
>> dependencies, including the two Alan mentioned. Did you install
>> print-manager explicitly, or was it pulled in by something else? I have 8
>> kde-base/*-meta packages installed but none of them have pulled in
>> print-manager.
>>
>> Printing seems to work well enough here since I connected my printers to my
>> workstation directly. My mini-server used to be a print server until a new
>> version of CUPS was released a few months ago. I couldn't get it to share
>> printers so I just moved them.
> 
> I have not to my knowledge installed a print-manager explicitly, so I assume 
> it was pulled in by one of the kde metas.
> 

$ equery depends print-manager
 * These packages depend on print-manager:
kde-base/kdeutils-meta-4.11.4 (cups ?
>=kde-base/print-manager-4.11.4:4[aqua=])


Set USE="-cups" to fix



-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2013-12-11 16:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07 10:16 [gentoo-user] Something is pulling in gnome-base Mick
2013-12-07 10:31 ` Tom Wijsman
2013-12-07 11:03   ` Mick
2013-12-07 11:27     ` Tom Wijsman
2013-12-07 11:47       ` Mick
2013-12-07 16:27         ` Tom Wijsman
2013-12-10 15:25         ` Walter Dnes
2013-12-10 23:40           ` Mick
2013-12-07 11:29     ` Peter Humphrey
2013-12-10 23:49       ` Mick
2013-12-11  7:38         ` Alan McKinnon
2013-12-11 10:58         ` Peter Humphrey
2013-12-11 16:29           ` Mick
2013-12-11 16:39             ` Alan McKinnon [this message]
2013-12-11 16:52               ` Peter Humphrey
2013-12-11 21:04                 ` Mick
2013-12-11 22:01                   ` Alan McKinnon
2013-12-12 10:01                   ` Peter Humphrey
2013-12-13  7:04                     ` Mick
2013-12-13  7:46                       ` Alan McKinnon
2013-12-13 10:49                       ` Peter Humphrey
2013-12-13 16:44                         ` Mick
2013-12-15  0:52                           ` Walter Dnes
2013-12-15  1:39                             ` Tom Wijsman

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=52A8955F.6090202@gmail.com \
    --to=alan.mckinnon@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