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

[Brian Inglis]

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