What about stabilizing current version of Rails? Has been in tree for almost two months. I am using 1.2 (1.2.2 and then 1.2.3) branch on both amd64 (Mongrel) and x86 (FastCGI) without any problem.
Required dependencies should be:
Sounds like a good idea to me, but I think it would be a good idea to keep rails-1.1.6 in the tree for a while longer for those people (like me) that still have production services running on 1.1.6. As it's slotted that should matter for stabilizing rails-1.2.3.
Stabilizing rake-0.7.2 should not be a problem given time and lack of open bugs.
rubygems is a bit more fickle and we only just unmased 0.9.2, so I propose to stabilize rubygems 0.9.0-r2 instead. However, I'm not sure if that version is actually problem-free. Nguyễn, perhaps you have beter insight in this?
Of course, this should be mainly for everyone who wants to use all nice features of 1.2. Keeping 1.1.6 is a good thing.
I am using 1.2.3 with rubygems-0.9.0-r2, works great also with other gems (mongrel, ruby-gettext etc.). Hope this helps :-)
It looks like the rubygems dependency is missing from the current rails-1.2.3
ebuild, but the changelog for Rails clearly states that it is mandatory.
This also means that rails can't go stable until rubygems-0.9.0-r2 has been
activesupport-1.4.2 depends on >=rubygems-0.9.0 maybe it is inough in this way?
The dependency for activesupport will at least ensure that rails-1.2.3 is not stabilized prematurely, but according to the changelog rails-1.2.2 and higher also depend on rubygems-0.9.0 or better, so this should be fixed at some point.
Add the rubygems 0.9.x bug 181322 as a dependency. Once this bug is resolved for all the arches I see no reason not to stabilize rails 1.2.3.
(In reply to comment #6)
> Add the rubygems 0.9.x bug 181322 as a dependency. Once this bug is resolved
> for all the arches I see no reason not to stabilize rails 1.2.3.
We still need to address the file collision with rails-1.1.x, ie bug 156092.
Did you or someone else already test the rails eselect module I attached to that bug?
1.2.3-r1 addresses the file collision issue, so now we need to wait 30 days before stabilizing. We should also do 1.1.6-r2 at that time as well.
It's been a bit over a month since we did -r1, and there hasn't been any issues.
We should be good to stabilize now.
Tested dev-ruby/rails-1.2.3-r1 USE="doc fastcgi mysql -postgres sqlite sqlite3" on sparc.
Using integrated webrick and www-servers/mongrel-1.0.1, sqlite db, sqlite3 db and mysql db.
Everything works fine.
Required dependencies are(all still testing):
# emerge --info
Portage 22.214.171.124 (default-linux/sparc/sparc64/2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.22-gentoo-l7-r5 sparc64)
System uname: 2.6.22-gentoo-l7-r5 sparc64 sun4u
Timestamp of tree: Fri, 05 Oct 2007 02:50:01 +0000
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.5, 1.7.9-r1, 1.9.6-r2, 1.10
CFLAGS="-mcpu=ultrasparc -mtune=ultrasparc -O2 -pipe"
CONFIG_PROTECT_MASK="/etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-mcpu=ultrasparc -mtune=ultrasparc -O2 -pipe"
FEATURES="collision-protect distlocks metadata-transfer parallel-fetch sandbox strict test userfetch userpriv usersandbox"
GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://mirror.muntinternet.net/pub/gentoo/ http://gentoo.ynet.sk/pub"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*"
USE="64bit 7zip a52 ace adns alsa amr berkdb big-tables bzip2 caps cgi chroot clamav clamd cli clock-screen courier crypt ctype custom-cflags cvs divx dnsdb doc dvd dynamic elf examples exim exiscan exiscan-acl extensions extraengine fast fastcgi fat flac gd ggi gif gzip hacking hddtemp highlight hpn httpd image imagemagick imap ipv6 ithreads jpeg jpeg2k key-screen l7filter lighttpd live logrotate maildir max-idx-128 mouse mp3 mp4live mpeg multiuser mysql mysqli ncurses net netserver network network-cron networking nls nonfsv4 noudev nowin nptl nptlonly ogg pcre php png posix raw-mode readline rtsp sasl screen scsi search-screen server session snmp spamassassin sparc spf ssl stream subversion suhosin svn-mirror symlink syslog szip test threads threadsafe threadsonly tiff unicode utf8 vcd vidix vim vim-syntax vnc vorbis web x264 xml xvid zip zlib" ALSA_CARDS="CS4231" ALSA_PCM_PLUGINS="adpcm alaw copy dshare dsnoop extplug file hooks ladspa lfloat linear meter mulaw multi null rate route share shm" ELIBC="glibc" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="sunffb"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
AS Friedrich noted this also requires version bumps (or stabilization at least) for:
With that, sparc stable. Thanks, Friedrich.
*** Bug 195315 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 195315 ***