public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [PATCH setup 0/2] Detect filename collisions between packages
Date: Thu, 27 Apr 2023 17:11:47 +0100	[thread overview]
Message-ID: <c035889e-200c-facf-190a-75d3d8af052b@dronecode.org.uk> (raw)
In-Reply-To: <87y1mh5end.fsf@Rainer.invalid>

On 24/04/2023 19:16, Achim Gratz via Cygwin-apps wrote:
> Corinna Vinschen via Cygwin-apps writes:
>> Calm could create a database containing all the files from the tar
>> archives it uploads, and compare that against the newly uploaded files
>> on the fly.
> 
> That already exists as the basis for package grep, albeit in the form of
> a buiinch of text files.
> 
> […]
>> There's probably another problem in terms of different file lists in
>> different package versions, though...
> 
> That is probably not too onerous to check for, but files moving from one
> package to another is a different story.

This is certainly doable.

(There's a few more wrinkles, as calm doesn't presently concern itself 
with trying to work out what the solver would install if you asked to 
install "everything", considering 'obsoletes:', and maybe even explicit 
'conflicts:' markers in hints, etc.)

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.


  reply	other threads:[~2023-04-27 16:11 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 [this message]
2023-04-28  5:51       ` Brian Inglis
2023-04-30 18:25         ` Jon Turney
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=c035889e-200c-facf-190a-75d3d8af052b@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).