From: Matthias Maier <tamiko@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] USE=desktop-file request
Date: Wed, 06 Jan 2016 22:59:13 +0100 [thread overview]
Message-ID: <87vb76mksu.fsf@jackdaw.kyomu.43-1.org> (raw)
In-Reply-To: <CAGfcS_=-noPuVWEkm-hkTUpGKep1ufUEbC76V6QqA2J_3hoy-g@mail.gmail.com> (Rich Freeman's message of "Wed, 6 Jan 2016 16:29:58 -0500")
> I'd have to check but I suspect that portage hangs onto build-time
> dependencies by default, probably so that you're not uninstalling them
> and reinstalling them anytime you do anything. Strictly speaking,
> however, it would be safe to depclean anything that is only a
> build-time dependency (with the understanding that you're going to be
> rebuilding it every time it is needed).
This behavior is controlled by the --with-bdeps=<y|n> option.
Best,
Matthias
next prev parent reply other threads:[~2016-01-06 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 16:23 [gentoo-dev] USE=desktop-file request tot-to
2016-01-06 18:59 ` Sergey Popov
2016-01-06 19:47 ` tot-to
2016-01-06 21:29 ` Rich Freeman
2016-01-06 21:59 ` Matthias Maier [this message]
2016-01-07 2:42 ` Peter Stuge
2016-01-09 8:24 ` Mart Raudsepp
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=87vb76mksu.fsf@jackdaw.kyomu.43-1.org \
--to=tamiko@gentoo.org \
--cc=gentoo-dev@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