fsprojects / fsprojects/Paket

Git Repo Dependencies: Dependent Transitive Packages Not Installed with Dependent Package (3.0.0-alpha040)

Open
#1,463 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When using the new git repo dependencies (example dependency files below)

I have a Package A which is dependent on Package B which is dependent on Package C (A->B->C). When I use packet install within Package B's directory it correctly grabs all dependencies (Package C) and puts them in the paket-files directory. So far so good.

Now when I run packet install on Package A, I would expect it to get all dependencies (Package B) and all of Package B's dependencies (Package C), which would be all dependencies in this example. However I only get dependency Package B. Ideally installing the top most package (Package A in this example) would install all dependencies as well.

Package A: /paket.dependencies
git http://notgithub.com/package/B.git

Package B: /paket.dependencies
git http://notgithub.com/package/C.git

Additional info:

  • Package B's package.dependencies file is in the root of the package's git repo.
  • As part of my use case, I do not commit the packet-files directory for Package B's to git.

Thanks!

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

Reproduce the A→B→C setup using the three paket.dependencies files described in the issue, then run packet install from Package A and inspect its paket-files directory. Trace how Package B's root dependency file is handled and verify that completing the fix installs both Package B and its transitive Package C dependency.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp, git
Domain
tooling
Issue type
Bug
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.