How to handle git/github dependencies project who use nuget internally
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Some projects that I add in packet.dependencies also have assemblies dependencies, but they use NuGet (for example JSON-RPC.NET need Newtonsoft.Json specified in packages.config).
So when I manually add JSON-RPC.NET as a project dependency in my application from Visual Studio, it doesn't compile because Newtonsoft.Json is not fetch.
Is their a way that packet can restore 'normal' nugget packages of git/github dependencies?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dependency described in packet.dependencies and compare its packages.config requirements, using JSON-RPC.NET and Newtonsoft.Json as the example. Reproduce the Visual Studio project scenario and trace Paket's handling of Git/GitHub dependencies; done means the normal NuGet dependency is fetched so the consuming application compiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, git, github
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100