How 'bout we just...
...don't ever write things in #Ruby.
I mean, whenever I try to install something written in Ruby, I run into problems I don't get with any other language.
The problem doesn't seem to be so much with the language itself as with the packaging system(s) that apparently everyone uses -- but the error messages are really unhelpful and leave me with no idea where to start.
The problem this time is some kind of undeclared function -- but searching the web for the function (so I could figure out what I need to install) just leads to other people trying to solve the same problem and never really getting to an understanding of what was causing it.
It also kind of feels like the people who do understand these things are almost proud of how tricky such problems are to fix and/or how little understanding they have of what the basic concepts are that one needs to understand in order to properly deal with such problems in the future.
To be fair, the last commenter in that thread did explain at least some of the problem.
In my case, it seems to be that I have ruby-mysql2 version 0.5.2 and for some reason it wants version 0.5.3. I don't know if that's what is causing the missing identifier, or if something is just barfing because it can't find the exact version it wants, or if I could just ignore that problem and move on now...
The Gemfile seems to think anything 0.5.x should be fine.
I seem to have gotten it to install by making the same change in about 4 places in 2 different files.
So now, whenever something automatically upgrades those libraries, everything will break again... and I'm not quite sure what installed them...
Can I submit a pull request? (Redmine uses subversion, but what does Ruby use?)
Also, the install documentation is out of date:
$ bundle install --without development test rmagick
--without flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use
bundle config set --local without 'development test rmagick', and stop using this flag
(...followed by the usual reminder not to run bundler as root even though it will probably need root privs at some point.)
@woozle Something even more subversive?
@woozle Sometimes I wonder if prior to ever release, we should take away the developers' machines and make them start over with fresh ones.
Just how many previously-unnoticed environmental assumptions would come to light?
@SetecAstronomy I vote for you as President of Software.
@woozle https://bugs.ruby-lang.org/projects/ruby/wiki/HowToContribute looks like they prefer you to open a redmine ticket, which will forward it to the mailing list.
@FiXato It looks like submitting a pull-request would be appropriate for these very small fixes -- but I feel like I should actually get my instance working first, just to establish that they're not breaking something further down in the process.
So far so good with the testing process...
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!