Long paths result in nonportable tar files
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system
Research direction
Start with boost/numeric/odeint/stepper/generation/generation_controlled_adams_bashforth_moulton.hpp and boost/numeric/odeint/stepper/generation/generation_runge_kutta_cash_karp54_classic.hpp, then trace references to both paths throughout the project. Check how the full paths appear when odeint is packaged as an R package. Done means the affected paths fit the CRAN tar limitation without breaking references.
Written by the indexing model from the issue text.
Description
This isn't really a bug, but the CRAN guidelines for R packages do not like paths with long file names since technically they are not supported by the tar format, which has a 100 byte limit. Most (or all?) modern tar implementations don't have a problem with this, so the complaint is annoying, but I was wondering if there is a sensible way to shorten some of the paths in Boost.
The two that cause a problem for me in particular are these:
"boost/numeric/odeint/stepper/generation/generation_controlled_adams_bashforth_moulton.hpp"
"boost/numeric/odeint/stepper/generation/generation_runge_kutta_cash_karp54_classic.hpp"
The "generation" portion is repetitive, so perhaps that could be removed from the file names?
Sorry for the irritating complaint.
EDIT: For clarification, the paths in boost are not longer than 100 bytes, but since they're part of an R package, the full path name is longer.
- Dominant language
- C++
- Stars
- 55
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
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 boostorg/odeint
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 43/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·