fsprojects / fsprojects/Paket

Specify git clone path

Open
#1,780 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement git up-for-grabs
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

Can we specify in the paket.dependencies file what path we want a git repo to be cloned into?

We're using some internal git repos. The URL of these are quite long. If repo A references repo B which references repo C, paket clones the repos in to a path which matches the URL. When its nested like A -> B -> C, we run into trouble because it exceeds the windows path size limit.

Repro steps
  1. Have projects A B and C in repos with a long URL
  2. Set up a git dependency from A -> B -> C, with a build script on each
  3. Clone repo A and do a paket install
Expected behavior

Build scripts should execute, git repos should download

Actual behavior

Build scripts and other things fail due to the path exceeding the windows limit

Known workarounds

None. We can't change the URL of the git repos unfortunately.

Related information
  • Operating system: Windows 10
  • Branch: latest
  • .NET Runtime: 4.5.2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the paket install flow on Windows and reproduce the nested A -> B -> C git dependencies using long repository URLs. Trace how paket.dependencies entries become clone paths and verify that a user-specified path lets the repositories download and their build scripts execute without exceeding the Windows path limit.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp, git
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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.