Feature Request: Paket Fetch
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
I've been thinking I'd like to dispense of nuget altoghether in favour of paket, but not having the ability to just fetch a nuget package (without the need for a paket.dependencies file) is holding me back.
So I propose a new command: "fetch" that does just that. Usage would be something like:
paket fetch mycomponent.2.4.6 output mydirectory source http://myinternal.nuget.server:89 source https://www.nuget.org/api/v2/
multiple sources allowed for transient 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
No files or tests are named in the issue. Start by locating Paket's command entry points and existing NuGet resolution flow, then trace how sources and transient dependencies are handled. Done means a fetch command accepts a package, output directory, and multiple sources without requiring a paket.dependencies file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100