From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT - Why does gcc depend on gtk+?
Date: Sun, 7 Jan 2007 12:31:02 -0700 [thread overview]
Message-ID: <7573e9640701071131q6cdfbdcdq196465787d5b920d@mail.gmail.com> (raw)
In-Reply-To: <1168196166.25769.4.camel@camille.espersunited.com>
On 1/7/07, Michael Sullivan <michael@espersunited.com> wrote:
> I wanted to free up some space on my server box. I was going through
> trying to find what packages could be safely removed. I don't have any
> graphical apps on my server box except gvim, which is built with -gtk.
> When I ran equery depends gtk+, it came up with gcc:
>
> bullet ~ # equery depends gtk+
equery depends is broken. It shows possible _dependancies_, without
taking USE flags into account.
Does gtk show up when you do a "emerge --depclean --pretend"?
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-07 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 18:56 [gentoo-user] OT - Why does gcc depend on gtk+? Michael Sullivan
2007-01-07 19:31 ` Richard Fish [this message]
2007-01-07 21:34 ` Bo Ørsted Andresen
2007-01-08 23:37 ` Paul Varner
2007-01-07 19:52 ` Etaoin Shrdlu
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=7573e9640701071131q6cdfbdcdq196465787d5b920d@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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