Excerpts from William Morgan's message of Wed Jan 09 20:02:47 +0100 2008: > That was my setup too. Weird that I no longer seem to have this problem. > > I've committed the following patch to next, which explicitly versions > bin/sup and lib/sup.rb and compares the two upon startup. Hopefully this > should detect this type of situation. For those of you who like to play > with sup via "rake gem", gems built from your checkout will have version > 999. (This was a suggestion Ian Taylor made a long time ago.)
Hi, That is a good idea imho, I have been doing something similar here. Currently `rake gem` fails here though with the following error: (using ruby-1.8.6_p111 & rake-0.7.3.) [EMAIL PROTECTED] /var/temp/portage/net-mail/sup-9999/work $ rake gem (in /home/temp/portage/net-mail/sup-9999/work) [Thu Jan 10 07:48:47 +0100 2008] using character set encoding "UTF-8" rake aborted! can't convert Fixnum into String /home/temp/portage/net-mail/sup-9999/work/Rakefile:15:in `new' Thank you _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
