-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gem build having some issues #563
Comments
Huh. Oddly, mine is working. Maybe some kind of version difference? |
Oh, interesting. No, a different branch was working, but main branch is borked. Okay, I'll look at this. |
Ah, okay. The whimsical checkout message from a bunny commit breaks it, because you changed the exe dir from 'exe' to 'bin'. Was hard to see because of all the lines that changed quotes. |
Ah, you also got rid of the webrick dependency. That's going to break at least one example on recent versions of Ruby, which no longer package webrick. |
Yeah, I mentioned in a PR I just put up that I'll be altering my editor to not format on save when working in this directory. I don't mind how our code is written and so if I'm disabling rubocop I should disable that as well! |
I think webrick is still there? Alright. closing this as eagle-eyed Noah caught the newly introduced mistake that caused failures. Thank you 🦅 🙇 |
Ah, Webrick moved/changed because of quoting but wasn't removed. Cool. |
I think it could have to do with this specification...
spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
The text was updated successfully, but these errors were encountered: