libyears metric should include age of Ruby and bundler

[sbleon]

Ruby and bundler are important dependencies. The current version of bundler can be ascertained from the end of Gemfile.lock. We can find the current Ruby version either in Gemfile, in .ruby-version, or by shelling out to run ruby -v.

[jaredbeck]

The current version of bundler can be ascertained from the end of Gemfile.lock

Hopefully bundler includes a parser for this, but I'm not opposed to using a regex either.

We can find the current Ruby version either in Gemfile, in .ruby-version, or by shelling out to run ruby -v.

The Gemfile should have precedence, I think.

[shanecav84]

bundler platform --ruby
"ruby 2.4.2p198\n"

[shanecav84]

Should the freshness of the Ruby version be included in the libyear calculation or have its own section?

[jaredbeck]

Should the freshness of the Ruby version be included in the libyear calculation or have its own section?

Let's include it in the main calculation with everything else. We don't make any distinctions between other dependencies. Let's treat ruby as just another dependency. The goal of this project is to calculate a single number. Simplicity above all else, you could say.

Of course, we can also have CLI options that change the calculation, or perform additional calculations, but the default should always be to calculate a single number.

[github-actions[bot]]

This issue has been automatically marked as stale due to inactivity. The resources of our volunteers are limited. Bug reports must provide a script that reproduces the bug, using our template. Feature suggestions must include a promise to build the feature yourself. Thank you for all your contributions.