Issue #6875 has been updated by vo.x (Vit Ondruch).


Hi guys,

Could you please enlighten what this issue solves? Adding .gemspec is not enough to create valid gem. The gem typically consist from following properties:

1) The /usr/bin stub allow to load specified version of gem, e.g. calling $ testrb _2.5.2_ should call the latest version of test-unit but your stub does not do so
2) The gem usually contains code. It does not depend on some code lying somewhere in the StdLib
3) The gem could be usually found on rubygems.org. While there is test-unit available on rubygems.org, it is definitely different test-unit then the one shipped with Ruby.

Could you please stop confusing Ruby users and stop to make life harder to us, packagers? I really love to have rubygem-test-unit in Fedora which is well defined and I'd really love to be able to break StdLib into independent rubygems, which can be packaged separately and updated separately, but this is not the way. Could you please reconsider your steps? Thank you.
----------------------------------------
Feature #6875: Make test/unit default gem
https://bugs.ruby-lang.org/issues/6875#change-30993

Author: kou (Kouhei Sutou)
Status: Closed
Priority: Normal
Assignee: sorah (Shota Fukumori)
Category: lib
Target version: 2.0.0


test/unit???default gem???????????????????????

http://bugs.ruby-lang.org/projects/ruby/wiki/StdlibGem ????????????????2.0.0.0???????????????

????test-unit???????gem????????????????test-unit gem??????????????????????????????????????????test/unit???????????????????test-unit gem?????使?????????????????????????????????????????????????



-- 
http://bugs.ruby-lang.org/