From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] [RFC] add emerge --changed-deps and --binpkg-changed-deps options, analogous to --newuse and --binpkg-respect-use
Date: Wed, 17 Dec 2014 17:54:02 -0800 [thread overview]
Message-ID: <549233BA.8090600@gentoo.org> (raw)
Hi,
The @changed-deps set is useful, but it has limitations similar to the
@installed set [1], which can make it unsuitable for use when updating
the whole system.
In order to solve the problems of @changed-deps, we can implement two
new options that are analogous to --newuse and --binpkg-respect-use,
called --changed-deps and --binpkg-changed-deps.
The rationale for having separate a --binpkg-* option is the same in
both cases: depending on the situation, people may want different
behavior for binary packages. For example, just like
---binpkg-respect-use is automatically enabled if the user has not
specified --usepkgonly, we could do the same for --binpkg-changed-deps
(but allow the user to explicitly override the automatic behavior).
Please respond if you agree or disagree with this proposal.
[1] https://bugs.gentoo.org/show_bug.cgi?id=387059
--
Thanks,
Zac
reply other threads:[~2014-12-18 1:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=549233BA.8090600@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-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