search

boostorg / odeint

Boost.odeint
Boost Software License 1.0
44 stars 54 forks source link

Long paths result in nonportable tar files #54

Open justinmcgrath opened 2 years ago

justinmcgrath commented 2 years ago

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.

justinmcgrath commented 11 months ago

We are not the only ones with this issue too. There's another R package that uses Boost, and the names need to be shortened for that as well: https://github.com/eddelbuettel/bh.

mborland commented 11 months ago

Once I get the CI system setup I can fix this for you. Are the paths short enough with just the redundant "generation" removed?

justinmcgrath commented 11 months ago

As of yesterday, there's a chance CRAN may increase this limit, so this may not be needed after all. I'll post here when I know their decision.