Suggestion: dependency order to package dependency table
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start at R/package.R around the pkg_deps_tree implementation referenced in the issue, then read the surrounding dependency data handling and the comment thread. Determine whether the result should expose an installation order or an additional column. Done means pkg_deps_tree provides enough dependency-order information for packages downloaded with pkg_download to be installed in a resolvable order.
Written by the indexing model from the issue text.
Description
I love pak! Its solving a real issue I have in a package for my work. But its missing a small thing for it to be my holy grail.
So, I have a package that downloads the source file of a package and source files for its dependencies, to prepare a zip file for import to an airgapped environment where the packages can be installed. pak creates a really lovely basis for this through pak::pkg_download .
The only thing I am missing, is somehow to know which order the packages should be installed in to resolve dependency issues as installing.
During pak::pkg_deps_tree you construct a tree
https://github.com/r-lib/pak/blob/main/R/package.R#L267
but then return the data without any indication of the order they depend on each other to help with something like this.
This could potentially solves by another column to the package dep data.frame, though it already is quite large, or if it was returned in their order to be installed, to resolve such issues?
- Dominant language
- C
- Stars
- 821
- Forks
- 88
- Avg merge
- 17m
- Merged PRs (30d)
- 1
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.
More from r-lib/pak
-
documentation upkeep
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·
-
bug Self Built Image SNAPSHOT Supported Device target/ramips
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100