Git as first class source
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Currently, as far as I can tell, Git is treated as a second class source within Paket. There is no way to specify transitive dependencies for a Git package. This is really counter productive. In a world of open source, Git should be treated more important than a last-resort fall back.
I love that I can use Paket to load a package from a Git repository, but that package should be able to specify dependencies as well and have them fufilled by Paket. That doesn't seem to be the case currently (or it is poorly documented if it is).
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 by reproducing Paket's handling of a package loaded from a Git repository and trace where its transitive dependencies are resolved. Compare that behavior with NuGet package dependency handling, then define tests showing that Git packages can declare and fulfill dependencies; done means those dependencies resolve reliably and the behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, git
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100