From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH setup 00/11] Improve handling of specifying an obsolete package to be installed on the command line
Date: Thu, 01 Aug 2019 16:05:00 -0000 [thread overview]
Message-ID: <20190801160519.32745-1-jon.turney@dronecode.org.uk> (raw)
e.g. setup -q -g -P python3-lxml (which used to do something useful)
currently gets you an (empty) python3-lxml package, which will be replaced
by python36-lxml (which obsoletes it) on the next setup run. After this
change, python36-lxml is installed instead.
See also the dicusssion at
https://cygwin.com/ml/cygwin-apps/2017-10/msg00092.html et seq. (where I
come to the (incorrect) conclusion that since we don't need this for
interactive use, it's not needed)
Jon Turney (11):
Remove 'Bin?' column
Remove unused packagemeta::key
Make packagemeta::message private
Rename 'Default' packagemeta action to 'NoChange' for clarity
Store the requested action in packagemeta::set_action()
Use packagemeta::set_action() to update action
Use stored action in setting up solver
Allow better handling of an obsolete package specified on command line
Use stored action in packagemeta::list_actions()
Use stored action in packagemeta::action_caption()
Ensure we only set user_picked when appropriate
PickCategoryLine.cc | 2 +-
PickPackageLine.cc | 32 +---------------
PickView.cc | 3 +-
PickView.h | 12 +++---
choose.cc | 9 ++---
libsolv.cc | 69 ++++++++++++++++++++-------------
libsolv.h | 1 +
package_db.cc | 4 +-
package_meta.cc | 93 ++++++++++++++++++++++-----------------------
package_meta.h | 16 ++++----
10 files changed, 113 insertions(+), 128 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-01 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 16:05 Jon Turney [this message]
2019-08-01 16:05 ` [PATCH setup 01/11] Remove 'Bin?' column Jon Turney
2019-08-01 16:05 ` [PATCH setup 02/11] Remove unused packagemeta::key Jon Turney
2019-08-01 16:06 ` [PATCH setup 03/11] Make packagemeta::message private Jon Turney
2019-08-01 16:07 ` [PATCH setup 05/11] Store the requested action in packagemeta::set_action() Jon Turney
2019-08-01 16:07 ` [PATCH setup 04/11] Rename 'Default' packagemeta action to 'NoChange' for clarity Jon Turney
2019-08-01 16:07 ` [PATCH setup 06/11] Use packagemeta::set_action() to update action Jon Turney
2019-08-01 16:08 ` [PATCH setup 09/11] Use stored action in packagemeta::list_actions() Jon Turney
2019-08-01 16:08 ` [PATCH setup 08/11] Allow better handling of an obsolete package specified on command line Jon Turney
2019-08-01 16:08 ` [PATCH setup 07/11] Use stored action in setting up solver Jon Turney
2019-08-01 16:09 ` [PATCH setup 10/11] Use stored action in packagemeta::action_caption() Jon Turney
2019-08-01 16:10 ` [PATCH setup 11/11] Ensure we only set user_picked when appropriate Jon Turney
2019-12-01 19:32 ` [PATCH setup 00/11] Improve handling of specifying an obsolete package to be installed on the command line Ken Brown
2019-12-03 20:44 ` Jon Turney
2019-12-03 21:16 ` Ken Brown
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=20190801160519.32745-1-jon.turney@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).