public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@Shaw.ca>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup 0/2] Detect filename collisions between packages
Date: Sun, 30 Apr 2023 19:25:41 +0100	[thread overview]
Message-ID: <a5c36bd3-5a31-6d53-2699-67b98e8e56ef@dronecode.org.uk> (raw)
In-Reply-To: <2fc159e2-2544-9e07-1f6b-8adadcdbe2f3@Shaw.ca>

On 28/04/2023 06:51, Brian Inglis via Cygwin-apps wrote:
> On 2023-04-27 10:11, Jon Turney via Cygwin-apps wrote:
[...]
>> I think this functionality needs to exist in setup as well, though, as 
>> calm can't possibly have knowledge of packages you might be installing 
>> from 3rd party overlay package repositories.
> 
> Please make any of these conflict messages warnings only, as few 
> packages use alternatives, and there may well be benign duplication, 

Your mention of 'alternatives' makes no sense to me.

The alternatives symlinks are not (and should not be) part of the 
package, but created or updated by postinstall scripts.

(It seems like it's impossible to make them work sensibly otherwise, as 
the link would be that from the most recently installed package (which 
could be any of the parallel installable alternatives), not the highest 
priority one.)

> e.g. multiple language versions, as we normally get complaints about 
> conflicts.

I don't know what this refers to.  Can you give an example?


  reply	other threads:[~2023-04-30 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 14:43 Jon Turney
2023-04-23 14:43 ` [PATCH setup 1/2] Add underlying() method to io_stream class Jon Turney
2023-04-23 14:43 ` [PATCH setup 2/2] Detect filename collisions between packages Jon Turney
2023-04-24 16:26   ` Christian Franke
2023-04-27 16:11     ` Jon Turney
2023-04-27 17:20       ` Christian Franke
2023-04-24 16:46 ` [PATCH setup 0/2] " Corinna Vinschen
2023-04-24 18:16   ` Achim Gratz
2023-04-27 16:11     ` Jon Turney
2023-04-28  5:51       ` Brian Inglis
2023-04-30 18:25         ` Jon Turney [this message]
2023-05-04  4:14           ` Brian Inglis

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=a5c36bd3-5a31-6d53-2699-67b98e8e56ef@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Brian.Inglis@Shaw.ca \
    --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).