From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 0/2] Detect filename collisions between packages
Date: Wed, 3 May 2023 22:14:43 -0600 [thread overview]
Message-ID: <5bdc2217-303a-1b2c-3f42-b342611eefd6@Shaw.ca> (raw)
In-Reply-To: <a5c36bd3-5a31-6d53-2699-67b98e8e56ef@dronecode.org.uk>
On 2023-04-30 12:25, Jon Turney wrote:
> On 28/04/2023 06:51, Brian Inglis wrote:
>> On 2023-04-27 10:11, Jon Turney 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?
As only a few packages use alternatives, and there may be multiple versions of
packages for different language versions, e.g. python3... there may be some
duplicate driver/selector file paths in some packages for different versions if
they may be installed in parallel, and later versions do not obsolete earlier.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2023-05-04 4:14 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
2023-05-04 4:14 ` Brian Inglis [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=5bdc2217-303a-1b2c-3f42-b342611eefd6@Shaw.ca \
--to=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).