From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup v2 0/2] Improve the handling of command line package selection
Date: Sun, 10 Jun 2018 20:58:00 -0000 [thread overview]
Message-ID: <ea790c7e-1c0c-7075-0750-7bfc7844d86b@dronecode.org.uk> (raw)
In-Reply-To: <20180607173724.5972-1-kbrown@cornell.edu>
On 07/06/2018 18:37, Ken Brown wrote:
> Suppose an installed package A gets updated because of the "--packages
> A" command line option. If A requires a version of package B higher
> than the installed version, then B will also need to be updated.
> Moreover, if the "--upgrade-also" option hasn't been specified, then
> the global update mode will be "Keep", so libsolv will have to add the
> upgrade of B.
>
> These two patches attempt to make sure that this process is handled
> smoothly. First, the package database needs to be set up so that it
> doesn't indicate that the user chose to keep B; this would cause
> libsolv to report a problem. Second, the "confirm" dialog should
> indicate that the upgrade of B was automatically added.
>
> v2: Rebase against current HEAD.
>
> Ken Brown (2):
> Improve the preparation of the package database
> Fix detection of automatically added packages
>
> choose.cc | 26 ++++++--------------------
> confirm.cc | 2 +-
> libsolv.cc | 11 +++--------
> package_db.cc | 12 ++++++++++++
> package_db.h | 2 ++
> 5 files changed, 24 insertions(+), 29 deletions(-)
>
Applied, thanks.
prev parent reply other threads:[~2018-06-10 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 17:37 Ken Brown
2018-06-07 17:37 ` [PATCH setup v2 1/2] Improve the preparation of the package database Ken Brown
2018-06-07 17:37 ` [PATCH setup v2 2/2] Fix detection of automatically added packages Ken Brown
2018-06-10 20:58 ` Jon Turney [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=ea790c7e-1c0c-7075-0750-7bfc7844d86b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).