Automatically `normalizePath()` for local type of references
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Begin with pkgdepends::pkg_refs() and the path handling reached by pak::pak(); compare the relative local reference example with normalizePath() output. Done means supported local references are automatically normalized and the shown pak::pak("../pkg2") case succeeds, with coverage for this behavior.
Written by the indexing model from the issue text.
Description
Given the following file structure:
my_packages/
├── pkg1
├── pkg2
├── pkg3
└── ...
I usually do:
setwd("my_packages/pkg1")
And then want to do the following:
pak::pak("../pkg2")
But it results in the following error:
Error:
! error in pak subprocess
Caused by error in `get_remote_types(refs)`:
! Cannot parse package:
../pkg2.
ℹ See `?pkgdepends::pkg_refs()` for supported
package sources.
Type .Last.error to see the more details.
The solution is to convert the path to be in absolute form via normalizePath(). This is definitely not the end of the world but involves a lot of typing given how short&sweet the pak::pak() command is.
My request is: can it be done automatically (for all local type of reference)?
- Dominant language
- C
- Stars
- 135
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/pkgdepends
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 4 comments ·
-
Allow trailing slash(es) in urls?Possibly taken @BjarkeHautop claimed this 97 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
r-lib/pkgdepends#477 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
r-lib/pkgdepends#486 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
r-lib/pkgdepends#484 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
r-lib/pkgdepends#483 · 1 comment ·
All issues in r-lib/pkgdepends
Similar issues
-
documentation severity: low
Difficulty 1/5 Under an hour Newbie friendliness 88/100
luainkernel/lunatik#2231 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/arrow-swift#209 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretiny-eu/libretiny#435 ·
Maintainers usually reply within 4 days
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
trezor/trezor-firmware#8210 ·
Maintainers usually reply within 3 days