Discussion: Official guidance on how to use Paket with .NET Core?
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
It seems like users of Paket waited a long time to use it without the dependency on Mono, and we've been able to do so for a few months now. However, it's not clear according to the docs whether there is a preferred method of using Paket in this new .NET Core world. Is it better to use it as a global tool? Or install it as a local tool in the /.paket directory and commit it?
My personal opinion is that we should encourage the use of Paket as a global tool. It seems like package managers in other language ecosystems don't require committing the package manager to the repo. I also think that it makes for a better user experience (i.e. paket add blah vs ./paket/paket add blah).
Do you have any thoughts on this?
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 reading the existing issue discussion and compare the global-tool and local-tool approaches described there. Done means the project has an agreed official recommendation for using Paket with .NET Core and that guidance is documented for users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100