How to resolve Package X is referenced though multiple groups

[apobekiaris]

Hi,

I am looking into groups in order to speed up new package installations/updates. According to docs I can update only one group. Trying to migrate my huge dependencies file I spitted dependecies per source. However when paket install i get

Package System.Runtime.CompilerServices.Unsafe is referenced through multiple groups in SomeProject (inspect lockfile for details). To resolve this warning use a single group for this project to get a unified dependency resolution or use conditions on the groups.

I fail to see how to efficient resolve such warnings? Should I create a new group containing only the packages for this project and assign them from there? Wouldn't that be a nightmare support? my strategy up to now is to share the same dependecies for all projects and would like to keep it like this. Also I fail to see how a group condition may applied at nothing is on the docs.

Any pointers much appreciated

[wnewbery]

@apobekiaris Did you come up with a solution for this?

Ran into it trying to figure out how should deal with projects that need different versions of certain specific things and reference a common class library in the solution, and as you say seems a maintenance nightmare to explicitly list all the common stuff in every group.

[apobekiaris]

unfortunately no shame to the power will lose at some point my current setup would be impossible to scale and was hopping to treat that with groups, but no idea how

[ghost]

I have the problem that i have a group with some packages which are used by analyzers. They need to use different versions of some packages because visual studio uses old collections apis internally. This gives me a about 100 warnings and i don't really know how to get away from this.

Obviously i don't want analyzers to influence what versions of packages i can use in my project,, which is why i have these in a separate group with copy_local: true. That seems to work fine, but yeah, anoying warnings.

I wish you could disable these warnings.