-
-
Notifications
You must be signed in to change notification settings - Fork 132
Make the progressbar and ruby-progressbar gems only differ in their names, but have the exact same content.#200
Open
npf wants to merge 2 commits intojfelchner:master from
Open
Make the progressbar and ruby-progressbar gems only differ in their names, but have the exact same content. #200npf wants to merge 2 commits intojfelchner:master from
npf wants to merge 2 commits intojfelchner:master from
Conversation
....rb or ruby-progessbar.rb Having the 2 gems with quite the same content but not exactly is very confusing, for instance on Debian because the ruby-progressbar deb package actually contains the progressbar gem, not the ruby-progressbar gem. IMHO, having both gems with the exact same content would be more user-friendly, allowing 'require "progressbar"' and 'require "ruby-progressbar"' indifferently from what gem is actually installed (be it with gem install or a distrubution package).
...ntent) It's the same content. Removes the duplication of code. Avoid possible divergence.
Owner
jfelchner
commented
Jun 3, 2025
@npf Why does the ruby-progressbar deb package contain the progressbar.gemspec file?
@npf Why does the
ruby-progressbardeb package contain theprogressbar.gemspecfile?
I believe the package is intended to contain the progressbar gem, but is named ruby-progressbar to disambiguate it from packages that provide similar libraries for other languages (such as python3-progressbar).
Or in other words, the same reason that the deb ruby-activerecord package contains activerecord-<version>.gemspec.
Owner
jfelchner
commented
Aug 27, 2025
Thanks for the reply! Unfortunately this is incorrect. progressbar and ruby-progressbar used to be two separate gems. They were merged a while back. The old standard of naming gems (ruby-progressbar is very old) was to start the gem name with ruby-.
@jfelchner
jfelchner
force-pushed
the
master
branch
7 times, most recently
from
January 8, 2026 05:03
fa75ebe to
bafa278
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
name: Pull Request
about: Make the progressbar and ruby-progressbar gems only differ in their names, but have the exact same content.
Let both the ruby-progressbar and progressbar gems allow requiring progressbar or ruby-progessbar indifferently.
Why: Having the 2 gems with quite the same content but not exactly is very
confusing, for instance, on Debian because the ruby-progressbar deb
package contains the progressbar gem, not the ruby-progressbar
gem.
IMHO, having both gems with the exact same content would be more
user-friendly, allowing 'require "progressbar"' and 'require
"ruby-progressbar"' indifferently, independently of what gem is actually installed
(be it with gem install or a distribution package).