Skip to content

Too long names for packaging: is this still a valid restriction? #5640

@rubyFeedback

Description

@rubyFeedback

Today I kind of created a new file for my gem called "studium".

When trying to package it I got this error:

ERROR:  While executing gem ... (Gem::Package::TooLongFileName)
    File         

"lib/studium/yaml/curricula/outdated/bachelor_bioinformatik_und_molekulare_biotechnologie_unter_berücksichtigung_medizinisch_immunologischer_aspekte.yml"

has a too long name (should be 100 or less) 
# oddly enough I can not even indent this via 4 ' ' here on github hehe ...
# when I do it simply makes a newline instead...

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?).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions