You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got warnings that both fiddle and rdoc had to be added to the Gemfile because they won't be in future Ruby 3.5 stdlibs. Not sure yet what that's all about. Add to bundle add them both to remove the warnings.
The text was updated successfully, but these errors were encountered:
I'm not sure about the fiddle warning, but the rdoc warning looks like it's coming from irb directly: https://bugs.ruby-lang.org/issues/20713#note-6. Checking that issue, I think what's meant by this comment is that if we were to add irb to the gemspec, we'd no longer get this warning.
I'd like to test this, but I'm not especially knowledgeable about gem development. I guess that I would need to update bridgetown-core/bridgetown-core.gemspec and re-build and re-install the gem. Doing so, however, I get symlink-related errors:
➜ gem install /bridgetown/bridgetown-builder-2.0.0.beta3.gem
ERROR: While executing gem ... (Gem::Package::SymlinkError)
installing symlink 'bridgetown-core/test/source/src/symlink-test/symlinked-file-outside-source' pointing to parent path /etc/passwd of /.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/bridgetown-builder-2.0.0.beta3 is not allowed
I could reject all symlink files in the gemspec, something like:
As an addition to the above, note that I only saw the warnings about fiddle and rdoc when running bin/bridgetown console, which led to me suspecting that this is irb-related.
I got warnings that both
fiddle
andrdoc
had to be added to the Gemfile because they won't be in future Ruby 3.5 stdlibs. Not sure yet what that's all about. Add tobundle add
them both to remove the warnings.The text was updated successfully, but these errors were encountered: