Closed andyundso closed 1 month ago
will check somewhere this weekend what is needed to get the Windows pipeline running.
The tests on Windows work now again: Instead of using gem install
into a temporary directory as we did before, I now use gem unpack
to extract the gem.
The tests on Windows work now again: Instead of using
gem install
into a temporary directory as we did before, I now usegem unpack
to extract the gem.
This seems weird, can you explain more what that's about? Also, I don't understand why we need a ci step to install bigdecimal manually if it's listed in the gemspec. Why wouldn't the normal gem install tiny_tds
process bring in that new dependency?
Also, I don't understand why we need a ci step to install bigdecimal manually if it's listed in the gemspec. Why wouldn't the normal gem install tiny_tds process bring in that new dependency?
Good point, gem install
should actually do that. I checked and most of our gem install
commands used --local
, which restricted the gem to download anything from the internet. This is removed now in the latest commit and the additional step to install bigdecimal is no longer required.
This seems weird, can you explain more what that's about?
I think gem unpack
is a more elegant solution to solve what we want to do, which is to extract the compiled files from the built gem.
This is to address the following warning on Ruby 3.3: