Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do I reference a Git dependency in my project? #3756

Open
njlr opened this issue Dec 17, 2019 · 1 comment
Open

How do I reference a Git dependency in my project? #3756

njlr opened this issue Dec 17, 2019 · 1 comment

Comments

@njlr
Copy link

njlr commented Dec 17, 2019

Description

I would like to use a Git dependency in my project. The Git repo contains .fsproj files, so I would expect referencing to be possible.

Repro steps

Please provide the steps required to reproduce the problem

  1. Add the Git dependency to paket.dependencies at the "solution" level.
git https://github.com/org/proj.git
  1. Install the packages.
dotnet paket install

Paket fetches the files and puts them into paket-files 👍

  1. Add the Git package to paket.references of my project.

How?

Expected behavior

I should be able to reference the Git dependency somehow.

Actual behavior

I cannot find a way to reference the Git dependency. The docs do not explain what to do.

Known workarounds

Create a NuGet package instead?

@kaashyapan
Copy link

kaashyapan commented Jul 25, 2020

Duplicate of #3064
The docs are not clear on this point.

hesxenon added a commit to hesxenon/Paket that referenced this issue Dec 31, 2022
with fsprojects#3756 and fsprojects#3064 it is quite clear, that the documentation around adding git repositories as a (usable) dependency isn't all that clear. Which is a pity, because the actual process isn't all that hard and also quite sensible-ish.

This change aims to slightly improve the docs and shed some light on this topic because - basically - all that is missing is some basic knowledge about how namespace/package resolution works in fsharp.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants