fsprojects / fsprojects/Paket

How to resolve Package X is referenced though multiple groups

Open
#3,854 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the documentation on dependency groups and group conditions, then reproduce the warning with paket install and inspect the lockfile as suggested. Done means the documentation clearly explains how to resolve shared dependencies across groups, including the dedicated-group and condition approaches raised here.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, tooling
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.