Too long names for packaging: is this still a valid restriction? #5645
Replies: 3 comments
-
I don't know. Feel free to investigate. |
Beta Was this translation helpful? Give feedback.
-
In all these years, nobody has ever needed or wanted to ship a file with a name 100 characters long inside a gem, so I doubt this will ever be implemented (if even possible) unless you implement it yourself. I'm going to move this to discussion since we're not even sure it's a valid (acceptable) feature request. |
Beta Was this translation helpful? Give feedback.
-
The 100 character limitation is inherited from the UStar ("Unix Standard TAR") standard, which is the newest standardized tar format. Each file or directory is stored in a tar file as a record, and the name of each record can only be 100 characters long. See https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html#tag_20_92_13_06 for details. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Today I kind of created a new file for my gem called "studium".
When trying to package it I got this error:
"lib/studium/yaml/curricula/outdated/bachelor_bioinformatik_und_molekulare_biotechnologie_unter_berücksichtigung_medizinisch_immunologischer_aspekte.yml"
I guess the file path also matters. But is this restriction still effective? If I remember correctly
this has been in place due to zlib from years ago? Perhaps that restriction could be dropped, or
alternatively, the threshold raised to 120 or something. Right now I move the
offending files away, build the .gem, upload it, then put the .yml files back in
place, but this is a bit tedious. This is why I'd love to see this restriction be dropped or
the threshold be lessened (not even sure why it is at 100? Is there a reason for
this or is that a magic number? 99? 101?).
Beta Was this translation helpful? Give feedback.
All reactions