boostorg / boostorg/odeint

Long paths result in nonportable tar files

Open
#54 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
55
Forks
59
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.