Group-level override?
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
(This is basically the same idea as #1386, but it appears to have been closed without a resolution.)
I'm looking for some way to override the remote server used when restoring packages.
The scenario I have is as follows:
We have an internal ProGet server which acts as a caching reverse proxy to the public NuGet gallery. This works wonders for internal developers, on-premises build servers, etc.
However, when a developer works remotely, we'd rather hit the public NuGet gallery as it would be faster than retrieving all the packages from ProGet over a VPN.
It seems that we have a couple options, none of which I like particularly much:
- Write or generate a
paket.localfile to override the source for each individual package - Manually modify the
restore:line inpaket.lock, taking care not to commit the modified file. - Modify the server URL in
paket.dependenciesand re-buildpaket.lock, taking care not to commit the modified files.
Is there any current method to override or supplement the restore server when running paket restore, either globally or on a per-group basis?
If not, what would it take to build such a method?
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 at the paket restore entry point and review how paket.dependencies, paket.lock, and paket.local currently determine package sources. Compare the earlier proposal in #1386, then define and validate a global or per-group remote override that supports the remote-developer scenario without requiring committed-file changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100