Bugzilla Bug 202013

rails is at version 2, the highest version even listed is 1.2.6.  No mention of
2.0 is made, it's not even masked.

Reproducible: Always

Steps to Reproduce:
1. navigate to http://packages.gentoo.org/package/dev-ruby/rails?
2. 
3. 

Actual Results:  
noted that version 2.0 isn't listed

Expected Results:  
that version 2.0 would at least be listed -- even if it were masked.

please at least update the website to acknowledge that 2.0 of rails has been
released.

(In reply to comment #0)
> please at least update the website to acknowledge that 2.0 of rails has been
> released.

Uh, the website takes data from portage tree, so it's absolutely correct.
There's no rails-2.0 *ebuild* anywhere.

There won't be a rails 2.0 ebuild ever, since this version has already been
superseded. We're working on rails 2.x ebuilds, but they probably won't make it
into the tree until this weekend at the earliest.

Also, in the future, please wait at least a week before filing new version
bugs... The maintainers of a package are usually aware and already working on
it.

Joshua, we need an updated eselect-rails as well. Can you take care of this?
Otherwise, is it under version control somewhere, or do I just take the current
source and hack a new version?

Hans: I don't have a dev environment setup at the moment, or I probably would
have worked through this over the weekend. I'll try to get a spare machine
setup tonight and see what I can do.

eselect-rails lives in
https://overlay.gentoo.org/svn/dev/nichoj/projects/eselect-rails

I've got the repository checked out and a new version ready to go on my dev
machine. Looking further at the ebuilds I think it makes sense to fix #198555
first, so that we only have to go through a change for the current 1.0 and 1.2
SLOTs, and can put the dependencies in the right spot for SLOT 2 right away.
Comments on that?

Also, should we still keep 1.0, or is it now ready to be punted from the tree.
I know I've converted all my projects and I consider myself to be a slacker
with that. :-)

I'm not convinced that we should have any db use flags, but I think #198555 is
right, they should be on activerecord if anywhere.

I think "we" should keep :1.1 in the tree until :2 is stable, BUT I'm not the
one that maintains all those builds.

Yeah, it seems like a good time to get in bug #198555 while doing the bump.

As for punting older versions, I don't think they really aren't doing us any
harm, and they don't require much care and tending at the moment, so there's
not much motivation to punt them. But we can discuss that on a yet-to-be filled
bug if people think we should punt it.

Just noticed they bumped it up to 2.0.2. Sure you guys are working hard on this
although, it would be nice to just skip 2.0.1 now if that is possible. 

Skipping to 2.0.2 sounds like a good idea. I hope to get to it within a few
days.

Hans, I have a dev machine up at last, so if you want to send me your changes
so far (particularly for eselect-rails), I can probably work through it
tonight.

Whoops, you already sent the patch for eselect-rails! It's committed to
https://overlay.gentoo.org/svn/dev/nichoj/projects/eselect-rails/trunk

Rails 2.0.2 is now in CVS, along with its dependencies.

Re-opening because we had to package.mask rails-2.0.x because of bug #202688.

Unmasked at last.