Re: [PATCH setup 0/2] Detect filename collisions between packages

[Brian Inglis <Brian.Inglis@Shaw.ca>]

On 2023-04-27 10:11, Jon Turney via Cygwin-apps wrote:
> 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.

Please make any of these conflict messages warnings only, as few packages use 
alternatives, and there may well be benign duplication, e.g. multiple language 
versions, as we normally get complaints about conflicts.

Alternatively, what about a report like Deprecated shared library packages 
https://cygwin.com/packages/reports/deprecated_so.html?

-- 
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