Ruby 2.0 (ruby20 in Gentoo) has been in the tree for over a month. It is the recommended version by upstream, so we would like to mark it stable now. At the moment we will not yet add it to RUBY_TARGETS because not enough packages have been marked for ruby20 yet. Having a stable version of ruby20 does make this process a lot easier, and we expect to add ruby20 to RUBY_TARGETS in a few months at the most. =dev-lang/ruby-2.0.0_p247-r1 =dev-ruby/rubygems-2.0.3 =virtual/rubygems-6 =dev-ruby/rake-0.9.6 =dev-ruby/json-1.8.0 =dev-ruby/racc-1.4.9 =dev-ruby/rdoc-4.0.1-r1 =virtual/ruby-minitest-0-r3 =virtual/ruby-rdoc-3
amd64 stable
x86 stable
after this change i get this (running amd64 stable profile): The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20] # required by dev-lang/ruby-2.0.0_p247-r1[rdoc] # required by dev-ruby/racc-1.4.9[ruby_targets_ruby20] # required by @selected # required by @world (argument) >=dev-ruby/json-1.8.0 ruby_targets_ruby20 # required by dev-lang/ruby-2.0.0_p247-r1 # required by dev-ruby/racc-1.4.9[ruby_targets_ruby20] # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby18] # required by @selected # required by @world (argument) >=dev-ruby/rake-0.9.6 ruby_targets_ruby20 # required by dev-lang/ruby-2.0.0_p247-r1 # required by dev-ruby/racc-1.4.9[ruby_targets_ruby20] # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby18] # required by @selected # required by @world (argument) >=dev-ruby/rubygems-2.0.3 ruby_targets_ruby20 # required by dev-lang/ruby-2.0.0_p247-r1[rdoc] # required by dev-ruby/racc-1.4.9[ruby_targets_ruby20] # required by @selected # required by @world (argument) >=dev-ruby/rdoc-4.0.1-r1 ruby_targets_ruby20 # required by dev-ruby/rdoc-4.0.1-r1[ruby_targets_ruby20] # required by dev-lang/ruby-2.0.0_p247-r1[rdoc] # required by dev-ruby/rubygems-2.0.3[ruby_targets_ruby19] # required by virtual/rubygems-6 # required by dev-ruby/rake-0.9.6 # required by dev-ruby/json-1.8.0[-test,-doc,ruby_targets_ruby18] # required by @selected # required by @world (argument) >=dev-ruby/racc-1.4.9 ruby_targets_ruby20 expected: portage doing the right thing (and pulling ruby 2.0 automatically if it has to) and not requiring me to manually fix things. if you break it, please do it on testing profile, thats what its for.
(In reply to groepaz from comment #3) > expected: portage doing the right thing (and pulling ruby 2.0 automatically > if it has to) and not requiring me to manually fix things. if you break it, > please do it on testing profile, thats what its for. If you don't know how to use gentoo, switch to ubuntu, thats what its for ;) The solution is add ruby20 to your RUBY_TARGETS. Please open a new bug if something does not look for you
(In reply to Agostino Sarubbo from comment #4) > (In reply to groepaz from comment #3) > > expected: portage doing the right thing (and pulling ruby 2.0 automatically > > if it has to) and not requiring me to manually fix things. if you break it, > > please do it on testing profile, thats what its for. > > If you don't know how to use gentoo, switch to ubuntu, thats what its for ;) > > The solution is add ruby20 to your RUBY_TARGETS. > > Please open a new bug if something does not look for you broken by default is not acceptable in gentoo. You really need to add ruby20 to RUBY_TARGETS or mask ruby 2.0.0 and remove the package.use.force on it. I've had dozens of reports from users in the last 18 hours.
> > expected: portage doing the right thing (and pulling ruby 2.0 automatically > > if it has to) and not requiring me to manually fix things. if you break it, > > please do it on testing profile, thats what its for. > > If you don't know how to use gentoo, switch to ubuntu, thats what its for ;) i am using gentoo for a long time now, thank you. long enough to assume that you can only be kidding, or somehow accidently got a hold of a developers email. > The solution is add ruby20 to your RUBY_TARGETS. > > Please open a new bug if something does not look for you and no. i dont even have RUBY_TARGETS in my make.conf (i can only guess you are referring to that), and in that case the right thing to do (for other packages that use similar mechanisms) has always been to simply use portage to update and it will do whatever it needs to do. i dont want to build god knows how many ruby packages for all 3 installed ruby versions (which will happen if i do what you say) but instead keep only - and exactly - the ones that are actually required. i also want to get rid of unneeded ruby crap whenever possible, which will only work this way. quoting the original post "At the moment we will not yet add it to RUBY_TARGETS because not enough packages have been marked for ruby20 yet." quoting you "The solution is add ruby20 to your RUBY_TARGETS" - it doesnt makes sense young padawan.
This needs to be unstabled until the RUBY_TARGETS fix goes in. Expecting users to install Ruby 2.0 because the Ruby team doesn't want to wait for that fix is NOT the proper thing to do. Please unstable it, or I will.
Would it be an option to enable ruby_targets_ruby20 via package.use in profiles, for the five packages mentioned in comment #3?
(In reply to Ulrich Müller from comment #8) > Would it be an option to enable ruby_targets_ruby20 via package.use in > profiles, for the five packages mentioned in comment #3? That is what the team attempted to do in base/package.use.force, clearly it isn't possible to cover all configurations. this needs to be fully enabled, or fully disabled, nothing in the middle is likely to actually work.
(In reply to groepaz from comment #6) > > If you don't know how to use gentoo, switch to ubuntu, thats what its for ;) > > i am using gentoo for a long time now, thank you. long enough to assume that > you can only be kidding, or somehow accidently got a hold of a developers > email. > I apologize for this stupid statement. I am sure Agostino did not mean it the way he said it. Regarding the issue: The decision to not add ruby20 to RUBY_TARGETS has proven to not be a good one, which we sadly only found out after the first arches went stable. We have discussed the issue and will be likely adding it tomorrow (UTC).
(In reply to Steev Klimaszewski from comment #7) > This needs to be unstabled until the RUBY_TARGETS fix goes in. Expecting > users to install Ruby 2.0 because the Ruby team doesn't want to wait for > that fix is NOT the proper thing to do. Please unstable it, or I will. The real bug here is that many packages still depend on dev-lang/ruby without any qualification. But we can't fix that quickly so we'll solve this on our end.
(In reply to Rick Farina (Zero_Chaos) from comment #9) > That is what the team attempted to do in base/package.use.force, clearly it > isn't possible to cover all configurations. this needs to be fully enabled, > or fully disabled, nothing in the middle is likely to actually work. This is not what we attempted at all so far, the list covering ruby virtuals is there for a different reason.
(In reply to Ulrich Müller from comment #8) > Would it be an option to enable ruby_targets_ruby20 via package.use in > profiles, for the five packages mentioned in comment #3? Thanks, that seems like the best approach we can take right now. I've added this to package.use.force.
Removing ARM until RUBY_TARGETS fix is properly done. While it may be okay for other arches to build and install ruby 2.0 "temporarily" until the fix is in, I don't wish to force that on our ARM users.
(In reply to Hans de Graaff from comment #13) > (In reply to Ulrich Müller from comment #8) > > Would it be an option to enable ruby_targets_ruby20 via package.use in > > profiles, for the five packages mentioned in comment #3? > > Thanks, that seems like the best approach we can take right now. I've added > this to package.use.force. This still isn't correct. Ruby defaults to rdoc being on by default. rdoc pulls in json. json force installs ruby 2.0. Please come up with a proper fix that will allow us to have systems without ruby 2.0 installed.
(In reply to Hans de Graaff from comment #13) > (In reply to Ulrich Müller from comment #8) > > Would it be an option to enable ruby_targets_ruby20 via package.use in > > profiles, for the five packages mentioned in comment #3? > > Thanks, that seems like the best approach we can take right now. I've added > this to package.use.force. The biggest (and only) problem here for me is this "best approach" solution. Please revert this! For others who want only ruby19 for now, I was able to fix this myself by adding the following to /etc/portage/profile/package.use.force dev-ruby/json -ruby_targets_ruby20 dev-ruby/racc -ruby_targets_ruby20 dev-ruby/rake -ruby_targets_ruby20 dev-ruby/rdoc -ruby_targets_ruby20 dev-ruby/rubygems -ruby_targets_ruby20 Now it seems to be working with RUBY_TARGETS="ruby19" in make.conf
I just masked ruby20, and didn't need to mess with any use flags at all.
Can people explain what the problem is with having ruby20 on your system already?
(In reply to Hans de Graaff from comment #18) > Can people explain what the problem is with having ruby20 on your system > already? They don't need the reason, the whole point of *_TARGETS it to let you choose which targets to enable.
(In reply to Hans de Graaff from comment #18) > Can people explain what the problem is with having ruby20 on your system > already? The issue is all the package.use.force stuff. We shouldn't be forced to use ruby20 when there is no need for it. If it's not optional, don't make it optional. Ignoring for a second the matter of choice (which is a big deal in gentoo last I checked), the fact that things DON"T WORK would be another minor detail. This bug reports like comment #3 that show you simply cannot get the deps right, so while you are FORCING users to install ruby20 you aren't even doing it right so people get locked into changing their RUBY_TARGETS since you didn't, or trying to mask ruby20 and remove all the package.use.force that you added. It's been said by others, I'll say it again, either add it to RUBY_TARGETS properly or just don't enable it on user systems. If gentoo users actually tried to use ruby this would be a tragedy, fortunately it seems very few bother.
Stable for HPPA.
SH is not anymore a stable arch, removing it from the cc list
S390 is not anymore a stable arch, removing it from the cc list
Please also include ruby-threads when ruby 2.0.x is stabled. >=dev-lang/ruby-2.0.0_p247-r1 >=dev-ruby/rubygems-2.0.3 =virtual/rubygems-6 >=dev-ruby/rake-0.9.6 >=dev-ruby/json-1.8.0 >=dev-ruby/racc-1.4.9 >=dev-ruby/rdoc-4.0.1-r1 =virtual/ruby-minitest-0-r3 =virtual/ruby-rdoc-3 =virtual/ruby-threads-4
ppc stable
ppc64 stable
ia64 stable
arm stable
sparc stable
alpha stable. Closing.
