public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] To be updated or not to be updated, Second Part
Date: Sun, 15 Sep 2013 14:32:16 +0100	[thread overview]
Message-ID: <20130915143216.52e0447e@digimed.co.uk> (raw)
In-Reply-To: <20130914061251.GA3655@solfire>

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

On Sat, 14 Sep 2013 08:12:51 +0200, meino.cramer@gmx.de wrote:

> Calculating dependencies... done!
> 
> Total: 0 packages, Size of downloads: 0 kB
> 
> Nothing to merge; quitting.
> 
> ------
> 
> beagleboneblack:/root>eix x11-libs/fox  
> [D] x11-libs/fox
>      Available versions:  
>      (1.6)  *1.6.40 *1.6.45 ~*1.6.49
>      (1.7)  ~*1.7.40 ~*1.7.41
>        {(+)bzip2 debug doc (+)jpeg (+)opengl (+)png profile tiff
> (+)truetype (+)zlib} Installed versions:  1.7.39(1.7)(23:22:36
> 08/07/13)(bzip2 jpeg opengl png truetype zlib -debug -doc -profile
> -tiff) Homepage:            http://www.fox-toolkit.org/
> Description:         C++ based Toolkit for developing Graphical User
> Interfaces easily and effectively
> 
> So, what is about x11-libs/fox? Delete it? Dont delete it?

emerge -cpv x11-libs/fox will ell you if anything depends on it. Chances
are it is a build time dependency of a package, which means portage won't
bother updating it until that package needs updating, unless you use
--with-build-deps=y.


-- 
Neil Bothwick

There is no such thing as an atheist in a foxhole.

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

      parent reply	other threads:[~2013-09-15 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14  6:12 [gentoo-user] To be updated or not to be updated, Second Part meino.cramer
2013-09-14 17:53 ` AR (aka AleiPhoenix)
2013-09-15 13:32 ` Neil Bothwick [this message]

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=20130915143216.52e0447e@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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