public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [setup topic/libsolv] Packages contained in multiple repositories
Date: Wed, 18 Oct 2017 16:41:00 -0000	[thread overview]
Message-ID: <87k1zs4dej.fsf@Rainer.invalid> (raw)
In-Reply-To: <9db21b28-18fa-603d-dec2-e49f72f9832e@cornell.edu> (Ken Brown's	message of "Wed, 18 Oct 2017 10:15:02 -0400")

Ken Brown writes:
> In retrospect, I'm not sure this patch is right, but I'm sending it
> anyway for the sake of discussion.  My hesitation comes from the fact
> that libsolv might have a good reason for preferring the one it chose,
> e.g., if we've assigned priorities to the repos.  On the other hand,
> if we've gone to the trouble of assigning priorities, shouldn't
> packagemeta reflect our choice?

Extrapolating from my experience with zypper, libsolv should stick with
the repo the installed package comes from even if some other repo has a
newer version.  The whole purpose of the "dup" command in zypper is to
lift that restriction (compared to the normal "up") and consider the
highest version from any repo as the preferred package (unless more
specific dependencies would yield a lower version or repo priorities
override the default algorithm).

This is often used for example to update just a single application to
something different from the main distribution: chose an extra repo,
install just one of many applications from that repo and then keep
updating the system normally.  The updates will come from your install
repo and just that single application will be updated from the extra
repo instead.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

  reply	other threads:[~2017-10-18 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 14:15 Ken Brown
2017-10-18 16:41 ` Achim Gratz [this message]
2017-10-19 13:36   ` Jon Turney
2017-10-19 17:14     ` Achim Gratz
2017-10-21 20:21     ` 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=87k1zs4dej.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).