Re: www/ruby-gtkmozembed uses obsolete seamonkey gecko provider
On Sun, 24 Oct 2010 15:12:06 +0200 Beat Gaetzi mentioned: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > The port www/ruby-gtkmozembed maintained by ruby@ uses the obsolete > seamonkey gecko provider. The seamonkey gecko provider will be removed > once SeaMonkey 2.1 is released. We expect this by the end of this year. > Could you please switch the gecko provider to libxul. If this port does > not work with libxul please remove the gecko dependency or remove the port. > I switched it to libxul, seems to work. -- Stanislav Sedov ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: rubygem-nokogiri and hoe
On Sun, 31 Oct 2010 12:38:01 +0900 Alexander Logvinov mentioned: > Hello! > > It doesn't seem to depend on hoe: > > https://rubygems.org/gems/nokogiri/versions/1.4.3 > > $ gem dependency nokogiri > Gem nokogiri-1.4.3.1 > hoe (>= 2.6.0, development) > minitest (>= 1.6.0, development) > racc (>= 0, development) > rake-compiler (>= 0, development) > rexical (>= 0, development) > rubyforge (>= 2.0.4, development) > You're right, it's a bogus dependency. I deleted it. Thanks! -- Stanislav Sedov ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: portupgrade-2.4.6_4,2 (patch for 'portsclean')
On Sat, 30 Oct 2010 12:06:22 +0200 Jürgen Galonska mentioned: > Hello, > > > would you mind applying the following patch to 'portsclean' from > portupgrade-2.4.6_4,2? > It fixes the problem of deleting all distfiles after the MD5/SHA256 > switch. > Hi! Thanks for the patch! I committed it and updated the port. -- Stanislav Sedov ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: [FIX] portupgrade fails if BEFOREDEINSTALL is set
On Sat, 20 Nov 2010 01:33:22 -0800
Joel Ray Holveck mentioned:
> In pkg_deinstall, in get_beforedeinstall_command, there's a line:
>
> commands.each { |cmd| cmd.sub!(/^[;\s]+/, '') if !cmd.nil }
>
> I'm kinda out of my area here, but I'm pretty sure that method should be
> "nil?", not "nil". As it stands, portupgrade fails to upgrade anything if
> BEFOREDEINSTALL in pkgtools.conf returns anything. (The example in the .conf
> file's comments returns a command for all packages, although it frequently is
> an empty string.)
>
> I've seen a couple of references to this by searching on Google, but I'm not
> aware of anybody having fixed it. The primary symptom is that portupgrade
> will build but during the deinstall will stop working on that package with no
> clear error message, and the reason given in the "why the upgrades failed"
> summary is "undefined method `nil' for "":String". I've seen people asking
> about this on freebsd-questions and freebsd-ruby, but haven't really searched
> that hard. (I cc'd the people I saw asking about it.)
>
> I'm sending this to r...@freebsd.org because that's what's listed as the
> maintainer for portupgrade; let me know if there's somewhere else it should
> go. I don't subscribe to the ruby list, and I apologize if this has been
> discussed here before.
>
> Please copy me on all replies, since I'm not on the list.
Thanks a lot for the patch, I'll look into this soon.
Sorry for delay, I was busy with my $dayjob.
Thanks!
--
Stanislav Sedov
ST4096-RIPE
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
pgpPB7IDU1i70.pgp
Description: PGP signature
Re: Ruby Symlink
On Fri, 10 Dec 2010 21:31:26 -0500 Charles Yoo mentioned: > I'm not sure if it was something that I did in particular, but did notice > that portupgrade stopped working for me, saying that ruby env was unknown > per: > > http://forums.freebsd.org/showthread.php?t=19874 > > I found that in /usr/local/bin there was no ruby symlink to ruby18, so that > was my fix. Mentioned that I should write you. Thanks, I fixed that in the latest revision of portupgrade! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: cvs commit: ports/devel/ruby-eet Makefile
On Thu, 16 Dec 2010 03:37:18 + (UTC) "Philip M. Gollucci" mentioned: > pgollucci2010-12-16 03:37:18 UTC > > FreeBSD ports repository > > Modified files: > devel/ruby-eet Makefile > Log: > - Fix shared library version. > Thanks! I'm wondering if we should deprecate this one actually, because it's not supported by upstream anymore. :-( -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: [ports-i...@freebsd.org: ruby18-refe-0.8.0 failed on i386 8]
On Fri, 24 Dec 2010 07:09:52 + "Philip M. Gollucci" mentioned: > On 12/23/10 13:46, Erwin Lansing wrote: > > > > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.8.20101223122716/ruby18-refe-0.8.0.log > > > > > ===> License check disabled, port has not defined LICENSE > > => refe-0.8.0-withdoc.tar.gz doesn't seem to exist in /tmp/distfiles/ruby. > > => Attempting to fetch from > > ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/. > > fetch: > > ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/refe-0.8.0-withdoc.tar.gz: > > File unavailable (e.g., file not found, no access) > > => Attempting to fetch from > > ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/. > > fetch: > > ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/refe-0.8.0-withdoc.tar.gz: > > File unavailable (e.g., file not found, no access) > > => Attempting to fetch from http://www.loveruby.net/archive/refe/refe/. > > fetch: http://www.loveruby.net/archive/refe/refe/refe-0.8.0-withdoc.tar.gz: > > Not Found > > => Attempting to fetch from > > ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/. > > fetch: > > ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/refe-0.8.0-withdoc.tar.gz: > > File unavailable (e.g., file not found, no access) > > => Attempting to fetch from > > ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/. > > fetch: > > ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/refe-0.8.0-withdoc.tar.gz: > > File unavailable (e.g., file not found, no access) > > => Couldn't fetch it - please try to retrieve this > > This looks right to me. I was mistaken about WITH_ flags, I saw the > -withdoc on the DISTNAME and figured it was NOPORTDOC related. > > My TB seems to build it okay and I have no local changes from CVS. > I'd check QAT but it seems down right now. > > Can you show me the contents of distinfo on pointy ? > It doesn't fetch here: % fetch http://www.loveruby.net/archive/refe/refe/refe-0.8.0-withdoc.tar.gz fetch: http://www.loveruby.net/archive/refe/refe/refe-0.8.0-withdoc.tar.gz: Not Found Maybe the distfile was removed? Then we should mirror it locally. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: RAKE_BIN and ruby19
On Dec 26, 2010, at 8:41 AM, Alexander Logvinov wrote:
> Hi!
>
> It seems this a typo:
>
> --- bsd.ruby.mk22 Nov 2010 05:47:07 -1.203
> +++ bsd.ruby.mk26 Dec 2010 16:32:33 -
> @@ -551,7 +551,7 @@
> .if ${RUBY_VER} == 1.8
> RAKE_BIN=${LOCALBASE}/bin/rake
> .else
> -RAKE_BIN=${GEM_LIB_DIR}/bin/rake${RUBY_VER:S/.//}
> +RAKE_BIN=${LOCALBASE}/bin/rake${RUBY_VER:S/.//}
> .endif
> .endif
>
> Also it can be:
>
> --- bsd.ruby.mk22 Nov 2010 05:47:07 -1.203
> +++ bsd.ruby.mk26 Dec 2010 16:34:47 -
> @@ -547,11 +547,11 @@
> .endif
>
> .if defined(USE_RAKE)
> -BUILD_DEPENDS+=${LOCALBASE}/bin/rake:${PORTSDIR}/devel/rubygem-rake
> .if ${RUBY_VER} == 1.8
> RAKE_BIN=${LOCALBASE}/bin/rake
> +BUILD_DEPENDS+=${RAKE_BIN}:${PORTSDIR}/devel/rubygem-rake
> .else
> -RAKE_BIN=${GEM_LIB_DIR}/bin/rake${RUBY_VER:S/.//}
> +RAKE_BIN=${LOCALBASE}/bin/rake${RUBY_VER:S/.//}
> .endif
> .endif
>
This change was made because we had problems with old version of rake
bundled with ruby 1.9. That's why we made it to always install rake, even
for 1.9. Or was it rubygem?
Why this is a promlem in any case? It seems that this path should point
to the right rake location for 1.9.
--
Stanislav Sedov
ST4096-RIPE___
freebsd-ruby@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Fwd: svn commit: r216916 - in user/dougb/portmaster: . files
On Sun, 02 Jan 2011 23:03:58 -0800 Doug Barton mentioned: > As discussed on the ports list I purposely picked a variable for this > knob that is not specific to portmaster in case anyone else wants to add > support for it as well. > Cool, thanks! I'll look into adding support for it in portupgrade. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/153965: [new port] security/rubygem-bcrypt-ruby : Sophisticated and secure hash algorithm for passwords
The following reply was made to PR ports/153965; it has been noted by GNATS. From: Stanislav Sedov To: Jason Helfman Cc: FreeBSD PR followup Subject: Re: ports/153965: [new port] security/rubygem-bcrypt-ruby : Sophisticated and secure hash algorithm for passwords Date: Thu, 13 Jan 2011 17:28:34 -0800 Hey! I'm wondering why did you named it rubygem-bcrypt-ruby and not just rubygem-bcrypt? For me the -ruby part looks bogus. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/154958: [REPOCOPY] databases/rubygem-sqlite3 --> databases/rubygem-sqlite3-ruby
Why we can't patch rubygem-rails-app-installer to use a proper library instead? The rubygem-sqlite3-ruby name looks ridiculous. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/154958: [REPOCOPY] databases/rubygem-sqlite3 --> databases/rubygem-sqlite3-ruby
On Thu, 3 Mar 2011 07:52:24 +0800 wen heping mentioned: > 2011/3/3 Stanislav Sedov : > > Why we can't patch rubygem-rails-app-installer to use a proper library > > instead? > Ok, then please patch it. > > > > The rubygem-sqlite3-ruby name looks ridiculous. > The name came from upstream, not ridiculous. > The upstream name is "sqlite3-ruby". Nobody is forcing us to add rubygems to our ports tree, there's always a plain version which is more universal and even preferrable. The app will continue to work anyway because it still 'require' a proper thing, it's the gem system itself that's the problem. And in any case, the port name doesn't have anything to do with the gem it installs. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments pgp1U3RNt0V1t.pgp Description: PGP signature
Re: making Ruby 1.9 default
On Wed, 16 Mar 2011 09:00:48 -0700 milki mentioned: > On 11:25 Wed 16 Mar , Eric wrote: > > There are plenty of outstanding PRs regarding portupgrade, which does seem > > to suffer from being both loved and unloved (in terms of maintenance). I > > personally use it, but am wondering if it's time to switch to Doug's > > PortMaster now... However given that portupgrade is often noted in > > documentation as almost the default tool for doing upgrades of ports then it > > does seem sensible that we should all try our best to fix it. > > I've been hanging out at #bsdports@efnet and I've gathered that is the > consensus of committers that portupgrade is no longer maintained and > portmaster is the preferred tool. The docs need some patching to reflect > this. > It's not true, it's officially maintained by ruby@, which for portupgrade was effectively mainly me for the past years. Unfortunately, I don't have enough resources to make significant changes there. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby Newbie...
On Wed, 16 Mar 2011 12:21:29 -0700 Glenn mentioned: > Good Day! I am attempting to install Jobsworth on FreeBSD 8.1-RELEASE > (amd64). It requires Ruby 1.9.x. > > I attempted to install Ruby and applicable gems via the ports > collection. Suffice to say that this procedure did not work. :-) My > next step was RTFM... > > In following the instructions at https://github.com/ari/jobsworth#readme > <http://www.google.com/url?sa=D&q=https://github.com/ari/jobsworth%23readme> > , I was able to get much further in the installation process! > > I was able to get to Step 5 (Ruby gems). The only way I could get Step > 5 (Ruby gems) to complete was to run the command as root although the > instructions wanted the commands run as my Apache user. > > When I run Step 6 (Setup configuration and database) and initialize the > database schema, I get: > Initialize database schema [n]: y > Initializing database schema > (in /usr/local/www/jobsworth) > rake aborted! > no such file to load -- iconv > /usr/local/www/jobsworth/Rakefile:4:in `' > (See full trace by running task with --trace) > (in /usr/local/www/jobsworth) > rake aborted! > no such file to load -- iconv > /usr/local/www/jobsworth/Rakefile:4:in `' > (See full trace by running task with --trace) > > Loading Rails to create account... > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/json-1.4.6/lib/json/common.rb: > 2:in `require': no such file to load -- iconv (LoadError) > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/json-1.4.6/lib/json/common.rb:2:in > `' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/json-1.4.6/lib/json.rb:1:in > `require' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/json-1.4.6/lib/json.rb:1:in > `' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.10/lib/bundler/runtime.rb:68:in > > `require' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.10/lib/bundler/runtime.rb:68:in > > `block (2 levels) in require' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.10/lib/bundler/runtime.rb:66:in > > `each' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.10/lib/bundler/runtime.rb:66:in > > `block in require' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.10/lib/bundler/runtime.rb:55:in > > `each' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.10/lib/bundler/runtime.rb:55:in > > `require' > from > /usr/local/rvm/gems/ruby-1.9.2-p180/gems/bundler-1.0.10/lib/bundler.rb:120:in > `require' > from /usr/local/www/jobsworth/config/application.rb:7:in ` (required)>' > from :29:in `require' > from :29:in `require' > from /usr/local/www/jobsworth/config/environment.rb:2:in ` (required)>' > from :29:in `require' > from :29:in `require' > from setup.rb:181:in `' > > I have attempted #2 from > http://exceptionz.wordpress.com/2010/02/03/how-to-fix-the-iconv-requi... > <http://www.google.com/url?sa=D&q=http://exceptionz.wordpress.com/2010/02/03/how-to-fix-the-iconv-require-error-in-ruby-1-9/> > > > . > > I have attempted > http://blog.dev001.net/post/2436585997/installing-iconv-using-bundler... > <http://www.google.com/url?sa=D&q=http://blog.dev001.net/post/2436585997/installing-iconv-using-bundler-on-freebsd> > > Neither has worked. I fear I am missing something simple. Alas, I > have zero Ruby experience prior to this project. Any assistance would > be greatly appreciated!!! :-) > It seems it missed the iconv library. Try installing it from converters/ruby-iconv. Also, if you're using ruby 1.9 set RUBY_VER to 1.9 when installing anything from ports. (e.g. via make variable, or put RUBY_VER=1.9 to the /etc/make.conf). -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: making Ruby 1.9 default
On Wed, 16 Mar 2011 19:31:36 -0700 milki mentioned: > On 13:42 Wed 16 Mar , Stanislav Sedov wrote: > > > I've been hanging out at #bsdports@efnet and I've gathered that is the > > > consensus of committers that portupgrade is no longer maintained and > > > portmaster is the preferred tool. The docs need some patching to reflect > > > this. > > > > > > > It's not true, it's officially maintained by ruby@, which for portupgrade > > was effectively mainly me for the past years. Unfortunately, I don't have > > enough resources to make significant changes there. > > Given that there are so many PRs and I emailed the official maintainer > (ruby@) with a small 2 line patch suggestion and received no feedback, > I'd say its pretty good as not maintained. Well, I just wanted to point out that officially it's maintained (at least I try to keep it working). The quality of maintainership is another question, and I agree that it's not acceptable. Unfortunately, none else stepped in to provide a mainteinership level of support after sem@ resigned. It certainly need a lot of love and care. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: making Ruby 1.9 default
On Thu, 17 Mar 2011 18:52:16 -0400 Steve Wills mentioned: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/16/11 07:25, Eric wrote: > >> From: paranormal > > [SNIP] > >> This is good idea. But beautiful port portupgrade :), > >> not work with 1.9 version. > > > > What about ports/144605 - "[PATCH] Get ports-mgmt/portupgrade to build under > > Ruby 1.9.1" > > > > I've not tried it, but does that patch do what it says on the tin? > > [...] > > > There are plenty of outstanding PRs regarding portupgrade, which does seem > > to suffer from being both loved and unloved (in terms of maintenance). I > > personally use it, but am wondering if it's time to switch to Doug's > > PortMaster now... However given that portupgrade is often noted in > > documentation as almost the default tool for doing upgrades of ports then it > > does seem sensible that we should all try our best to fix it. > > > > I personally think we should still aim to get to the default of 1.9 and > > aiming for the 9.0 release seems a sensible target to go for, if part of > > that process would seem to be getting portupgrade sorted then so be it. > > Portupgrade is a bit of a problem. Perhaps it's due to my patches, but > at the moment I can't get databases/ruby-bdb to build with RUBY_VER == > 1.9. If I could get past that, I could test the above PR. I wonder if > anyone else has the same issue. > It does not work with 1.9. I submitted some pacthes to fix it, but it's not enough to get it build. IIRC, there were some other problems knu@ mentioned. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ruby 1.9 update patch
On Wed, 25 May 2011 07:54:21 -0400
Steve Wills mentioned:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thanks for the feedback!
>
> I was attempting to do some run time testing of this and stumbled upon a
> strange issue. It seems that even without my patch (and with it too), if
> you do this:
>
> cd /usr/ports/databases/ruby-bdb
> env RUBY_VER=1.9 make install
>
> on a system without any ruby, it will install Ruby 1.9, then fail to
> install the databases/ruby-bdb port since there will not be a "rdoc"
> binary installed, but only "rdoc19". My patch doesn't make this worse,
> but it doesn't help it either. Should I try to solve this and if so how?
It should use ${RUBY_RDOC} instead of just calling rdoc directly.
This way it will get the correct one.
--
Stanislav Sedov
ST4096-RIPE
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
___
freebsd-ruby@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Status of migration to ruby 1.9 as default
On Wed, 06 Jul 2011 22:28:00 -0400 Steve Wills mentioned: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > In case anyone is interested, here's where we are with migrating to Ruby > 1.9 as the default version: Thanks for a nice summary. Seems like a lot of work has been done. So when do you want to make the switch? I'm still not sure it's the right time to do it as part of 9.0 release cycle, as it seems that some of the important ports are broken and people still using 1.8 for production (myself included). WRT rdoc -- is there really a way to make ruby19 not install rdoc? My impression was that rdoc now is part of ruby and this is the way to go... Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Rails 3.1.0.rc4
On Thu, 7 Jul 2011 11:58:28 +0100 Simon Dick mentioned: > Don't suppose anyone has test packages for this version? I need to > deploy something with it urgently but haven't had much luck manually > updating the 3.0.9 ports to hack it together. > I don't have packages, but maybe we can help to overcome the update problem? What was the error that prevented you from updating your ports? -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/158827: devel/rubygem-rdoc: fix compatibility with ruby 1.8
> RDoc 3.6 is still compatible with ruby 1.8, although it was lately marked as > BROKEN for ruby 1.8. > The NetBSD guys have fixed the problem for pkgsrc: It actually installs fine for me if I just kill the RUBY_VER= 1.9 line. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/158827: devel/rubygem-rdoc: fix compatibility with ruby 1.8
The following reply was made to PR ports/158827; it has been noted by GNATS. From: Stanislav Sedov To: Frank Wall Cc: r...@freebsd.org, FreeBSD PR followup Subject: Re: ports/158827: devel/rubygem-rdoc: fix compatibility with ruby 1.8 Date: Tue, 12 Jul 2011 12:17:36 -0700 > RDoc 3.6 is still compatible with ruby 1.8, although it was lately marked as > BROKEN for ruby 1.8. > The NetBSD guys have fixed the problem for pkgsrc: It actually installs fine for me if I just kill the RUBY_VER= 1.9 line. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/158827: devel/rubygem-rdoc: fix compatibility with ruby 1.8
On Tue, 12 Jul 2011 23:14:07 + "Philip M. Gollucci" mentioned: > On 07/12/11 19:20, Stanislav Sedov wrote: > > > RDoc 3.6 is still compatible with ruby 1.8, although it was lately > > marked as BROKEN for ruby 1.8. > The NetBSD guys have fixed the problem for > > pkgsrc: > > > > It actually installs fine for me if I just kill the > > RUBY_VER= 1.9 > > line. > Something else is amiss. Feel free to revert if you think it helps. > Well, I don't want to until I know it's safe... -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Time to mark portupgrade deprecated?
> Why pick portupgrade when a lot of people (including myself) use it? There > are > probably 100's of ports more worthy of deprecation. Maybe there should be a > policy to deprecate all unmaintained ports if nobody steps up. You can always > drag it out of the attic if enough people squak and probably find someone to > maintain it in the process. > Personally, I don't see any reason at all to deprecate it. It works, it's maintained (by ruby@ and me personally) and it's generally useful. If someone feels that there's lack of maintainership here he's always welcome to step in and contribute time/resources. -- ST4096-RIPE___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: RFC: Replacing graphics/ruby-rmagick with graphics/rubygem-rmagick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 30 Jul 2011 22:30:07 -0400 Ryan Steinmetz mentioned: > All, > > I am planning on removing graphics/ruby-rmagick and replacing it with > graphics/rubygem-rmagick, pending maintainer/mentor approval. > > They both install the same library (RMagick2.so), however, the rubygem > registers with the gem framework. Without it being registered as a gem, > other ruby applications which depend on the gem consider it not to be > installed and complain. > > As a result, I believe that the best course of action is to update the > dependencies in the two ports that depend on ruby-rmagick > (graphics/rubygem-gruff and www/redmine) and remove > graphics/ruby-rmagick, replacing it with graphics/rubygem-rmagick. > > I'd welcome any thoughts/feedback you may have. > > I do not have any attachments to being the MAINTAINER for > rubygem-rmagick, so if stas@ (or anyone else) is interested in it, > please let me know. > I don't think it's a good idea. It might looks fine from the rubygems camp side, but for projects not using rubygems it means that you wouldn't be able to do 'require rmagick' and do the work. Even worse, for non-rubygems applications you will need to run it via `ruby -rrubygems /path/to/app` instead of just `app`. As an example of this try running bluecloth from the rubygem-bluecloth package: % ruby /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.1/bin/bluecloth /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.1/bin/bluecloth:15:in `require': no such file to load -- bluecloth (LoadError) from /usr/local/lib/ruby/gems/1.8/gems/BlueCloth-1.0.1/bin/bluecloth:15 Personally, I'm not in favor of having these two ports either, I actually requested the removal of rubygem- version immediately upon commit: http://www.mail-archive.com/cvs-all@freebsd.org/msg149854.html Not sure why it didn't happen though. But since other ports now depend on it, we probably cannot do it anymore. :-( - -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -BEGIN PGP SIGNATURE- iQIcBAEBAgAGBQJONaHFAAoJEL8lojEJL9nwY8IQAMbH6dO3R8gAeKavaOXYE0SN it/MbUX5gJeLMZySAx8zS1FkuAQ1c5EXVWE/wobW/x7RMRNwk9OScxIA0UsEBAHx vpDq9DR8wjj7NB1alp4n79n2Bur9DPE2ZL+5ploRrUs+q0+oIKzQvTgOUlwvllbi CjyTEvbGxtZeavJACMqAiA9xt3J0VoGC53Mc9aNCjjoFh04No3zyMPnMgT8LMLmf d+dvdl5Wxq1fNvJtU2StRVozLTGuHYiafxcT+4q0V5xjjARatzzAa4WTy9mWn1Kl sIKJUOL5v++cEShWEhxvHlZRSSFpXSZsExcpR/p7Y4Gvf/gfyOrmwEJ5e6EJp0bH S5OAP7jLXKMXG+LHt4COtgN9XjNnJVtk1+N1jdkEpCiwGWgDTtwnPOGmnRLTPcg0 0Am+ELPl+1YCoP6OhNXwKgy+D4MQc4JkfOouQwr0fX/tn7mjRueUQJHLpS7x+SYO kIIuabeaG8Qu8//+IH75WZCCeJuqeKfGi18Sst7cshv0qHeuUv/HvZSaE7WhDbpG T83dOnqlOBWxqRFX3+uLiK4sUvDCX207y2IUH93BMAyRpnEr8DWz+csU3sPZnpus Yl82E+OQsbWKubFexIPSyWqq5Za+ELYJ2WHsN7Uhqm5MIDpMP1ge8GgbDqyif2lh 8RrBjhrf771+IsZSnmK4 =Brbj -END PGP SIGNATURE- ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: RFC: Replacing graphics/ruby-rmagick with graphics/rubygem-rmagick
On Sun, 31 Jul 2011 15:58:00 -0400 Ryan Steinmetz mentioned: > > Perhaps the attached shar(1) meets the needs of both? > > I compared the locations of the files that ruby-rmagick installs with the gem > and > simply generate symlinks to fill in the gaps. > > The end result is that the rubygem port should be able to meet the needs > of both. > -require rmagick should work > -rmagick is registered as a gem and available to other gems > > If others agree on the tactic, it's possible that we could incorporate > the concept into bsd.ruby.mk and automatically enable it via a knob. > Then, simply convert everything else to use the rubygems framework. > Thanks, his looks like one of possible solutions. I'm not sure we will be able to propagate something like this into the bsd.ruby.mk though, as it might not be always clear which files to symlink where. There's another problem with gems though -- the lack of customisability. If we convert rmagick to gem, we won't be able to apply custom patches to it, or it will be extremely difficult. E.g. right now we apply some patches to accomodate our ImageMagick version and to make ruby-rmagick port PREFIX clean (that is that it will install into any prefix, even different from where the ruby port was installed). How would we handle this with the gem version (or any other problems we'll need to fix) -- I don't know. Is there any way we can patch this snorby to pick up the rmagick version installed from ports instead of querying the gem database? -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 this weekend
On Fri, 19 Aug 2011 20:09:32 -0400 Steve Wills mentioned: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > I'm mailing you because you are listed as part of the ruby@ team on > http://wiki.freebsd.org/Ruby. > > The last exp-run of my patch to make Ruby 1.9 default was very clean. > There are still a good number of ports that are marked as broken with > 1.9, but none too critical as far as I can tell. > > Unless there are objections, I plan to go ahead and commit my patch to > make 1.9 the default this time tomorrow. Once it's committed, I'll keep > an eye on lists and bug reports to catch anything I might have missed. > > What say you? Silence will be taken as acceptance. :) > Sounds fine by me, but I suggest sending HEADS UP to ports@ several days before this happens and listen for replies. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
ruby-gems update
Hi!
I'd like to update our ruby-gems versio to 1.8.7.
Are there any objections? It seems that everything is
working fine with this version, and it includes a lot of
bugfixes, including better behaviour with ruby 1.9.2.
I'm attaching the patch I'm planning to commit. If there's
no objection, I will commit it tomorrow.
The patch also fixes the issue when rdocs were not installed
due to unexsisting directory (it also produced a broken plist
when you already had this directory, because it would not
include those files).
Thanks!
--
Stanislav Sedov
ST4096-RIPE
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Index: Makefile
===
RCS file: /home/pcvs/ports/devel/ruby-gems/Makefile,v
retrieving revision 1.43
diff -u -r1.43 Makefile
--- Makefile 23 Aug 2011 03:47:28 - 1.43
+++ Makefile 28 Aug 2011 09:59:21 -
@@ -6,7 +6,7 @@
#
PORTNAME= gems
-PORTVERSION= 1.7.2
+PORTVERSION= 1.8.7
CATEGORIES= devel ruby
MASTER_SITES= RF
MASTER_SITE_SUBDIR= ruby${PORTNAME}
@@ -20,14 +20,14 @@
USE_RUBY= yes
RUBY_SETUP= setup.rb
-RUBY_VER= 1.8
NO_BUILD= yes
-PLIST_SUB+= DISTNAME="${DISTNAME}"
+PLIST_SUB+= DISTNAME="${DISTNAME}" \
+ RUBY_VER_SHORT="${RUBY_VER_SHORT}"
.if !defined(NOPORTDOCS)
-RUBY_SETUP_OPTIONS=
+RUBY_SETUP_OPTIONS= --ri --rdoc
.else
RUBY_SETUP_OPTIONS= --no-ri --no-rdoc
.endif
@@ -40,6 +40,7 @@
GEMS_DOC_BASE_DIR_P= ${GEMS_VER_DIR_P}/doc
GEMS_DOC_DIR= ${GEMS_DOC_BASE_DIR}/${DISTNAME}
GEMS_DOC_DIR_P= ${GEMS_DOC_BASE_DIR_P}/%%DISTNAME%%
+RUBY_VER_SHORT= ${RUBY_VER:S/.//}
.include
@@ -48,13 +49,24 @@
.endif
do-install:
+ @${MKDIR} ${PREFIX}/${GEMS_DOC_BASE_DIR}/
+ @${TOUCH} ${PREFIX}/${GEMS_DOC_BASE_DIR}/.keep_this
cd ${WRKSRC}; ${RUBY} ${RUBY_SETUP} ${RUBY_SETUP_OPTIONS}
post-install:
- @${MKDIR} ${PREFIX}/${GEMS_DOC_BASE_DIR}/
- @${TOUCH} ${PREFIX}/${GEMS_DOC_BASE_DIR}/.keep_this
- @${LN} -sf ${PREFIX}/bin/gem18 ${PREFIX}/bin/gem
+ @${LN} -sf ${PREFIX}/bin/gem${RUBY_VER_SHORT} ${PREFIX}/bin/gem
+
+#
+# Find all RDOC and RI files
+#
+.if !defined(NOPORTDOCS)
+ @${FIND} -ds ${PREFIX}/${GEMS_DOC_DIR}/ ! -type d | \
+ ${SED} 's,^${PREFIX}/,,' >> ${TMPPLIST}
+ @${FIND} -ds ${PREFIX}/${GEMS_DOC_DIR}/ -type d -mindepth 1 | \
+ ${SED} -E -e 's,^${PREFIX}/,@dirrm ,' >> ${TMPPLIST}
+.endif
+ @${ECHO_CMD} "@dirrm ${GEMS_DOC_DIR}" >> ${TMPPLIST}
@${ECHO_CMD} "@unexec rmdir %D/lib/ruby/gems/${RUBY_VER}/doc 2>/dev/null || true" >> ${TMPPLIST}
@${ECHO_CMD} "@unexec rmdir %D/lib/ruby/gems/${RUBY_VER} 2>/dev/null || true" >> ${TMPPLIST}
@${ECHO_CMD} "@unexec rmdir %D/lib/ruby/gems 2>/dev/null || true" >> ${TMPPLIST}
@@ -63,11 +75,8 @@
# This target is only meant to be used by the port maintainer.
x-generate-plist:
${ECHO} bin/gem > pkg-plist.new
- ${ECHO} bin/gem18 >> pkg-plist.new
- ${ECHO} bin/update_rubygems18 >> pkg-plist.new
- ${ECHO} ${GEMS_VER_DIR_P}/cache/sources-0.0.2.gem >> pkg-plist.new
- ${FIND} ${PREFIX}/${GEMS_VER_DIR}/gems/sources-0.0.2 -type f | ${SORT} | ${SED} -e 's,${PREFIX}/${GEMS_VER_DIR},${GEMS_VER_DIR_P},' >> pkg-plist.new
- ${ECHO} ${GEMS_VER_DIR_P}/specifications/sources-0.0.2.gemspec >> pkg-plist.new
+ ${ECHO} bin/gem%%RUBY_VER_SHORT%% >> pkg-plist.new
+ ${ECHO} %%RUBY_SITELIBDIR%%/gauntlet_rubygems.rb >> pkg-plist.new
${ECHO} %%RUBY_SITELIBDIR%%/rbconfig/datadir.rb >> pkg-plist.new
${ECHO} %%RUBY_SITELIBDIR%%/rubygems.rb >> pkg-plist.new
${FIND} ${RUBY_SITELIBDIR}/rubygems -type f | ${SORT} | ${SED} -e 's,${RUBY_SITELIBDIR},%%RUBY_SITELIBDIR%%,' >> pkg-plist.new
@@ -77,11 +86,10 @@
${FIND} ${RUBY_SITELIBDIR}/rubygems -type d | ${SORT} -r | ${SED} -e 's,${RUBY_SITELIBDIR},@dirrm %%RUBY_SITELIBDIR%%,' >> pkg-plist.new
${ECHO} @dirrm %%RUBY_SITELIBDIR%%/rbconfig >> pkg-plist.new
${ECHO} @dirrmtry ${GEMS_VER_DIR_P}/specifications >> pkg-plist.new
- ${FIND} ${PREFIX}/${GEMS_VER_DIR}/gems/sources-0.0.2 -type d | ${SORT} -r | ${SED} -e 's,${PREFIX}/${GEMS_VER_DIR},@dirrm ${GEMS_VER_DIR_P},' >> pkg-plist.new
${ECHO} @dirrmtry ${GEMS_VER_DIR_P}/gems >> pkg-plist.new
${ECHO} @dirrmtry ${GEMS_VER_DIR_P}/cache >> pkg-plist.new
${FIND} ${PREFIX}/${GEMS_DOC_DIR} -type d | ${SORT} -r | ${SED} -e 's,${PREFIX}/${GEMS_DOC_DIR},%%PORTDOCS%%@dirrm ${GEMS_DOC_DIR_P},' >> pkg-plist.new
- ${ECHO} ${PREFIX}/${GEMS_DOC_BASE_DIR}/.keep_this >> pkg-plist.new
+ ${ECHO} ${GEMS_DOC_BASE_DIR_P}/.keep_this >> pkg-plist.new
${ECHO} @dirrmtry ${GEMS_DOC_BASE_DIR_P} >> pkg-plist.new
${ECHO} @dirrmtry ${GEMS_VER_DIR_P} >> pkg-plist.new
${ECHO} @dirrmtry ${GEMS_BASE_DIR_P} &g
Re: ruby-gems update
On Sun, 28 Aug 2011 07:07:43 -0400 Steve Wills mentioned: > Long term I think we should consider a move away from using the version > prefixes and support only one version of ruby installed at a time. > I don't agree. It allows one to experiment with different ruby version w/out affecting the dependent software. It's also very useful in the production as well, where you often need to run different software backed by different ruby vm's. That's exactly why I impelemented this mechanizm when importing ruby 1.9 (which reminds me that I need to add rubinius support as an alternative VM as well). -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby port advice needed [Was: rubyripper-0.6.0_1 failed on amd64 9]
On Thu, 1 Sep 2011 08:28:16 + Alexey Dokuchaev mentioned: > Hi there, > > There is a ruby-written port I maintain, and several months ago it was > working just fine. However, apparently, our default Ruby bits got updated > or something, and now it currently does not build as quoted in pointyhat > log below (trimmed for your convenience). > > I'm not a Ruby expert; perhaps someone can take a look and explain what > should be done to remedy the problem? > > Thanks, > > ./danfe > Hi! It turned out the ruby-gettext method your port is using has triggered a bug in the new version of rubugems. I filed the issue with the upstream. Nonetheless, the Gem::all_load_paths method gettext is using is deprecated, so we probably need to patch it in the gettext anyway. Unfortunately, it seems that upstream no longer supports this library, so I'll try to figure out how to patch the gem port tomorrow. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: portupgrade problem
On Tue, 6 Sep 2011 15:49:42 -0400 "Jason Seidel" mentioned: > Recently when I tried updating my ports, i get the following error: > > [Updating the portsdb in /usr/ports ... - 22741 port entries > found > .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000... > HASH: Out of overflow pages. Increase page size > error] Remove and try again. > [Updating the portsdb in /usr/ports ... - 22741 port entries > found > .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000... > HASH: Out of overflow pages. Increase page size > > > And just keeps on going, what can i do to fix this problem? Hi! Is it running under ruby 1.8 or ruby 1.9? Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Fw: Re: portupgrade problem
On Wed, 7 Sep 2011 13:08:50 -0400 "Jason Seidel" mentioned: > Something happened to portupgrade, its not even recognizing ruby 1.9, the > problem is it installed 1.8, so I had 2 versions of ruby and its causing it to > mess up. I uninstalled ruby 1.8 and reinstalled ruby 1.9; but portupgrade > doesnt even look for 1.9 and tries to put 1.8 back again. > > Something got messed up in the port. Hi! This is the expected behavior, because the default ruby version has been reverted back to 1.8 after being 1.9 for a couple of days. If you'd like to keep 1.9 as default, just add RUBY_DEFAULT_VER=1.9 to make.conf as instructed in UPDATING. Don't be afraid that you have two versions of ruby installed -- they can coexists successfully. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: portupgrade-devel issue
On Mon, 12 Sep 2011 22:36:16 +0200 Pav Lucistnik mentioned: > Hi folks, > > this came up on pointyhat. Can you fix portupgrade-devel port to stop > spamming /usr/ports/distfiles (or whatever $DISTDIR happens to be) with > files that are not listed in distinfo? > > I see you're doing some creative things with git, it can live in /tmp > instead I suppose... > Hi! Sorry for that. What kind of extra files do you see? It's not supposed to do this... -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: portupgrade-devel issue
On Mon, 12 Sep 2011 23:06:38 +0200
Pav Lucistnik mentioned:
> Stanislav Sedov píše v po 12. 09. 2011 v 14:01 -0700:
> > On Mon, 12 Sep 2011 22:36:16 +0200
> > Pav Lucistnik mentioned:
> >
> > > Hi folks,
> > >
> > > this came up on pointyhat. Can you fix portupgrade-devel port to stop
> > > spamming /usr/ports/distfiles (or whatever $DISTDIR happens to be) with
> > > files that are not listed in distinfo?
> > >
> > > I see you're doing some creative things with git, it can live in /tmp
> > > instead I suppose...
> > >
> >
> > Hi!
> >
> > Sorry for that.
> > What kind of extra files do you see? It's not supposed to do this...
>
> ls -l portupgrade-devel-,2/portupgrade/latest
> lrwxr-xr-x 1 ports-amd64 wheel 44 Sep 11 07:07
> portupgrade-devel-,2/portupgrade/latest ->
> /tmp/distfiles//portupgrade/pkgtools-.tar.gz
>
Hmm.
What is the "portupgrade-devel-,2" dir? According to the makefile it
creates the symlink
in the ${_DISTDIR} for the file in the ${_DISTDIR}.
For the missing version -- I just realized that I probably need to add fetch
depends...
--
Stanislav Sedov
ST4096-RIPE
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
___
freebsd-ruby@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: devel/rubygem-json146 deletion
On Thu, 27 Oct 2011 13:48:26 -0400 "Steve Wills" mentioned: > Hi, > > Now that I've updated the datamapper and rails ports, I think the > devel/rubygem-json146 port can go away. Does anyone see a reason not to > delete it? > Go ahead and kill it. Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby on Rails and new jQuery question?
On Tue, 8 Nov 2011 23:15:47 +0200 Andrew Stesin mentioned: > Dear Ruby maintainers! > > May I ask just a small question. A few days ago a new jQuery was > released; how soon will it come to FreeBSD rubygem-jquery-rails port? > > Thanks in advanсe, and thanks for doing good job for us all :) > Hi! As far as I know nobody is actively working on it. You're welcome to try to update it and send us a patch though, or even become the port maintainer if you're an active user of it. Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: What changed? (gem command missing in 1.9)
On Fri, 11 Nov 2011 14:55:06 -0700 "Aaron D. Gifford" mentioned: > Hi, > > I've been using RUBY_DEFAULT_VER=1.9 in my /etc/make.conf for months > now successfully to ensure that gem, ri, irb, ruby, etc. were > correctly symlinked in /usr/local/bin/ to the *19 commands. However > today upon building the /usr/ports/lang/ruby19 port and installing it > afresh, I discovered that the other *19 commands are there EXCEPT for > the gem command: > > user@host:/usr/local/bin$ ls -ld *19 > -rwxr-xr-x 2 root wheel 4401 Nov 11 14:48 erb19 > -rwxr-xr-x 2 root wheel 322 Nov 11 14:48 irb19 > -rwxr-xr-x 2 root wheel 701 Nov 11 14:48 rdoc19 > -rwxr-xr-x 2 root wheel77 Nov 11 14:48 ri19 > -rwxr-xr-x 2 root wheel 5448 Nov 11 14:48 ruby19 > -rwxr-xr-x 2 root wheel 251 Nov 11 14:48 testrb19 > user@host:/usr/local/bin$ ls -l erb irb rdoc ri ruby testrb gem > ls: gem: No such file or directory > -rwxr-xr-x 2 root wheel 4401 Nov 11 14:48 erb > -rwxr-xr-x 2 root wheel 322 Nov 11 14:48 irb > -rwxr-xr-x 2 root wheel 701 Nov 11 14:48 rdoc > -rwxr-xr-x 2 root wheel77 Nov 11 14:48 ri > -rwxr-xr-x 2 root wheel 5448 Nov 11 14:48 ruby > -rwxr-xr-x 2 root wheel 251 Nov 11 14:48 testrb > > What happened? What changed? Where did the gem command go? Is there > a new environment variable I need while building the port now? > Hi! The gem version distributed in ruby 1.9 is too old for some ports, so FreeBSD uses the rubygem from ports instead. To get the gem command back just install the ruby-gems port. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: What changed? (gem command missing in 1.9)
On Fri, 11 Nov 2011 16:52:07 -0700 "Aaron D. Gifford" mentioned: > I'm not familiar with the inner workings of FreeBSD's port system, but > is it possible that issues like 'gem' and 'rake' suddenly no longer > being part of the lang/ruby19 port (due to the aforementioned outdated > versions) could be dealt with during some sort of post-install hook > while installing the lang/ruby19 port, a hook that could then install > devel/ruby-gems and devel/rubygem-rake ports so that the executables > that previously were always part of lang/ruby19 will still be > automatically installed with that port? > Yes, we can actually do that. We're discussing the possibility of making lang/ruby19 to depend on ruby-gems and rake, thus having ruby19 installation automatically install rake and gem as well. But nobody did that yet. I agree tought that should have been done at the moment the gem binary was dropped from ruby19, but I think we just forgot about this at the end. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: What changed? (gem command missing in 1.9)
On Fri, 11 Nov 2011 21:32:30 -0500 Steve Wills mentioned: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 11/11/11 21:18, Stanislav Sedov wrote: > > Yes, we can actually do that. We're discussing the possibility of making > > lang/ruby19 to depend on ruby-gems and rake, thus having ruby19 installation > > automatically install rake and gem as well. But nobody did that yet. > > > > I agree tought that should have been done at the moment the gem binary > > was dropped from ruby19, but I think we just forgot about this at the > > end. > > > > Does the attached simple patch (untested) cover it or is more needed? > I believe it might do. I'm not sure though you can run depend on something that build depends on you, so it needs testing. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: redmine-1.2.1_1 is still broken
On Fri, 02 Dec 2011 16:24:02 +0100 Bernhard Froehlich mentioned: > On 09.11.2011 21:41, Philip M. Gollucci wrote: > > On 11/9/11 12:23 PM, Bernhard Froehlich wrote: > >>> Tue Nov 1 23:55:41 2011 UTC (7 days, 20 hours ago) by pgollucci > >>> > >>> - Unmark broken, it works just fine > >>> $ cd /var/db/pkg ; ls -1d redmine-1.2.1 ruby1* > >> > >> That is not true. It is still broken and you obviously missed the > >> point. > >> > >> > >> www# cd /usr/local/www/redmine ; rake db:migrate > >> RAILS_ENV=production > >> --trace > > This exact line works flawlessly for me which is why I did what I > > did. > > That's nice and we should probably find out why it works only for you. > Probably > you have integrated some patch or the bug needs some special trigger? > > It definitely doesn't work for anyone that I have talked to and a PR > came in > yesterday complaining about this problem. So I decided to jump into > that and > mark the port BROKEN again so people know what they can expect. That's > better > than shipping a broken redmine with 9.0-RELEASE. > > I hope nobody feels offended because I'm not the maintainer of redmine > anymore > and I'm also not wearing a ruby hat but there was no action about this > problem > in the last month and it doesn't look like anybody cares about redmine. > Hi! What is the problem with redmine is? I might look into this over the weekend. Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: [lini...@freebsd.org: cvs commit: ports/security/flowtag Makefile ports/www/redmine Makefile]
On Fri, 16 Dec 2011 21:28:20 -0600 Mark Linimon mentioned: > I was testing RUBY_VER=1.9 on pointyhat-west and ran into these two > cases of duplicate dependencies. I'm hoping the "oh yeah, pretty > obviously wrong as-is" incantation will work for doing a commit without > checking first. (redmine is broken anyways for other reasons.) > > mcl > Looks good to me. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: [Fwd: ruby18-bz2-0.2.2_1 failed on amd64 8]
JFYI, ri generates random filenames which depend on the file system for ordering. That's why we replaced all plists in rubygems by automatic ones a while ago. Otherwise maintainers would just put static filenames into plist, and committees blindly commit them. I'm pretty sure the same happened here possibly pointyhat is using ZFS, and plist was created on UFS. -- ST4096-RIPE On Jan 23, 2012, at 4:29 PM, "Steve Wills" wrote: > Me too. I get intermittent failures and can't pin it down yet. Testing to > see if it's a MAKE_JOBS issue right now. > > Steve > >> I'm quite perplexed. >> >> http://people.freebsd.org/~pgollucci/FreeBSD/logs/9-CURRENT-amd64-ruby/ruby18-bz2-0.2.2_1.log >> >> >> >> On 01/23/12 21:39, Pav Lucistnik wrote: >>> Pøeposlaná zpráva Od: User Ports-amd64 Komu: c...@oook.cz, ite...@freebsd.org, florent.thou...@gmail.com Pøedmìt: ruby18-bz2-0.2.2_1 failed on amd64 8 Datum: Mon, 23 Jan 2012 16:45:05 GMT You can also find this build log at http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.8.20120123091558/ruby18-bz2-0.2.2_1.log building ruby18-bz2-0.2.2_1 on gohan62.freebsd.org in directory /y/pkgbuild/8/20120123091558/chroot/20 building for: 8.1-RELEASE-p4 amd64 maintained by: r...@freebsd.org port directory: /usr/ports/archivers/ruby-bz2 Makefile ident: $FreeBSD: ports/archivers/ruby-bz2/Makefile,v 1.21 2011/11/01 22:59:31 pgollucci Exp $ build started at Mon Jan 23 16:43:48 UTC 2012 FETCH_DEPENDS= PATCH_DEPENDS=ruby-1.8.7.357,1.tbz EXTRACT_DEPENDS=ruby-1.8.7.357,1.tbz BUILD_DEPENDS=ruby-1.8.7.357,1.tbz RUN_DEPENDS=ruby-1.8.7.357,1.tbz prefixes: LOCALBASE=usr/local add_pkg ===> License check disabled, port has not defined LICENSE => bz2-0.2.2.tar.gz doesn't seem to exist in /tmp/distfiles/ruby. => Attempting to fetch ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/ruby/bz2-0.2.2.tar.gz bz2-0.2.2.tar.gz16 kB 889 kBps => SHA256 Checksum OK for ruby/bz2-0.2.2.tar.gz. add_pkg ruby-1.8.7.357,1.tbz adding dependencies pkg_add ruby-1.8.7.357,1.tbz Note that some of the standard libraries are provided as separate ports since they require extra dependencies: converters/ruby-iconviconv module databases/ruby-gdbm:GDBM module x11-toolkits/ruby-tk:Tcl/Tk modules japanese/ruby-tk:Tcl/Tk modules for Japanized Tcl/Tk lang/ruby-mode.el:Emacs lisp modules Install them as occasion demands. ===> License check disabled, port has not defined LICENSE ===> Extracting for ruby18-bz2-0.2.2_1 => SHA256 Checksum OK for ruby/bz2-0.2.2.tar.gz. ===> ruby18-bz2-0.2.2_1 depends on file: /usr/local/bin/ruby18 - found Deleting ruby-1.8.7.357,1 add_pkg ruby-1.8.7.357,1.tbz adding dependencies pkg_add ruby-1.8.7.357,1.tbz Note that some of the standard libraries are provided as separate ports since they require extra dependencies: converters/ruby-iconviconv module databases/ruby-gdbm:GDBM module x11-toolkits/ruby-tk:Tcl/Tk modules japanese/ruby-tk:Tcl/Tk modules for Japanized Tcl/Tk lang/ruby-mode.el:Emacs lisp modules Install them as occasion demands. ===> Patching for ruby18-bz2-0.2.2_1 ===> ruby18-bz2-0.2.2_1 depends on file: /usr/local/bin/ruby18 - found Deleting ruby-1.8.7.357,1 add_pkg ruby-1.8.7.357,1.tbz adding dependencies pkg_add ruby-1.8.7.357,1.tbz Note that some of the standard libraries are provided as separate ports since they require extra dependencies: converters/ruby-iconviconv module databases/ruby-gdbm:GDBM module x11-toolkits/ruby-tk:Tcl/Tk modules japanese/ruby-tk:Tcl/Tk modules for Japanized Tcl/Tk lang/ruby-mode.el:Emacs lisp modules Install them as occasion demands. ===> ruby18-bz2-0.2.2_1 depends on file: /usr/local/bin/ruby18 - found ===> Configuring for ruby18-bz2-0.2.2_1 ===> Running extconf.rb to configure checking for BZ2_bzWriteOpen() in -lbz2... yes creating Mak
Re: ruby 1.8.7p358 and ruby 1.9.0p125
On Thu, 16 Feb 2012 23:36:14 -0500 Steve Wills mentioned: > Hi All, > > If anyone is interested in trying the updated ruby 1.8.7p358 or ruby > 1.9.3p125 which were both released today, I have a patch here: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=165223 > > Builds fine and passes tests, and as you can see in the PR, there is an > exp-run requested for it, but extra testing won't hurt. > Which tests? Does it pass the rubyspec regression test suite? Did you look at possible regression in rubyspec compared to the previous release? Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Something wrong with inst
On Tue, 29 May 2012 10:21:04 +0400 "Oleg simonoff" mentioned: > Hi! > Got some troubles with instalation ruby-1.8.7-p358 > > Please, let me know, what mast i do > > See the attached file Something is wrong with your C compiler, it fails when running % cc -I/usr/include -o1 -pipe -I/usr/include -L/usr/lib -rpath=/usr/lib:/usr/local/lib -pthread conftest.c -L/usr/lib -rpath=/usr/lib:/usr/local/lib -pthread Please, check your make.conf settings. It's not clear why it fails from the configure.log, but you may try running the command by hand with conftest.c contents being one from configure.log and see where and why it fails. BTW, are you using something else than GCC by any chance? -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 as default
On Fri, 01 Jun 2012 21:32:53 -0400 Steve Wills mentioned: > Hi All, > > I think we should try to make Ruby 1.9 the default Ruby again and would > like to see it done before 9.1 is released. I've submitted a patch which > does this and requested and exp-run from portmgr. > > I would like to get feedback on this idea. If you have experience with > Ruby 1.9 as default, good or bad, please speak up. You can test this by > setting RUBY_DEFAULT_VER=1.9 in /etc/make.conf or editing Mk/bsd.ruby.mk > and setting the same variable there. > I'm not sure it's a good idea. Ruby 1.9 still has some nasty bugs on FreeBSD, related to the threads and fork. That is fork in ruby 1.9 hangs sometimes... OTOH, I've been running ruby 1.9 as default on both of my desktops and have not seen major problems except this one. Still, it'd be nice for someone to fix it first (I remember there were a lot of eager commiters at the time I gave up my commit bit). The main question is whether the switch to 1.9 will be beneficial for our users. Apart from some libraries targeting 1.9 exclusivly now, most of of them still work with 1.8 and there're still some that work with 1.8 only. Given that most of the ports users mostly care for 3rd party applications to work, I'm not sure if the switch to 1.9 will be a win for them... -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 as default
On Jun 5, 2012, at 1:52 AM, Konstantin Belousov wrote: > On Mon, Jun 04, 2012 at 08:25:08PM -0400, Steve Wills wrote: >> On 06/01/12 22:30, Stanislav Sedov wrote: >>> >>> I'm not sure it's a good idea. >>> Ruby 1.9 still has some nasty bugs on FreeBSD, related to the threads and >>> fork. That is fork in ruby 1.9 hangs sometimes... >> >> The ONLY thing I can find is this: >> >> http://bugs.ruby-lang.org/issues/2097 >> >> which implies that it's fixed. If there's more to this issue than >> "broken on 7.3 and earlier", PLEASE let me know. > > If ruby indeed does what the bugs described, that is, calls non-async > signal safe functions from the threaded process after fork, then you > are guaranteed to get random hangs sometimes. Actually, the problem I'm trying to debug right now is more weird. When I run mono via system(3) from the ruby 1.9 process (I mean, exactly system(3), not via some ruby wrapper) twice, it hangs on some umtx the second time. This works all the time. I'm still trying to track it down in mono, though it's not clear how this can happen at all. Isn't execve(2) used by system(3) is supposed to clear everything (mutexes at least)? Thanks! -- ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 as default
On Tue, 5 Jun 2012 09:43:55 -0400 "Steve Wills" mentioned: > > > > Is this perhaps the -pthread issue I hit with perl? The issue is that if > you call (dlopen, exec, whatever) a threaded app from a non-threaded on, > it hangs due to the fact that libc takes shortcuts and doesn't initialize > thread related things in non-threaded apps. The solution is to build with > -pthread. (I may be describing the problem wrong, but the solution of > building with -pthread works.) You usually cannot dlopen the object linked agains pthread from a non-pthreaded object. Or it is used to be that way. Exec should work fine, I don't see how this can be an issue. > > Perhaps we need to build ruby with -pthread? > Of course, we already do. Both of them. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 as default
On Tue, 5 Jun 2012 11:42:09 +0200 Romain Tartière mentioned: > On Tue, Jun 05, 2012 at 02:04:33AM -0700, Stanislav Sedov wrote: > > Actually, the problem I'm trying to debug right now is more weird. > > When I run mono via system(3) from the ruby 1.9 process (I mean, > > exactly system(3), not via some ruby wrapper) twice, it hangs on some > > umtx the second time. This works all the time. > > > > I'm still trying to track it down in mono, though it's not clear how > > this can happen at all. Isn't execve(2) used by system(3) is supposed > > to clear everything (mutexes at least)? > > Hum... mono hanging... I experience this with Banshee this is why it s > marked IGNORE: > http://www.freshports.org/multimedia/banshee/ > > I used to see the mono process in the "STOP" state, but last time I > tried it was in the "umtx" state. Requesting a backtrace from mono make > it abort, attaching gdb to it also fails. The problem happenning after > a random amount of time (a few minutes, a few hours) I have not been > able de localise the source of the problem yet. If you have > experiencing the same problem but can reproduce it, it's a HUGE step > forward! Can you please provide me a minimal working example ? I tried > to jack something but it works as expected :-/ > Hi! Sounds similar. Unfortunately, my app is proprietary. I'll try to prepare some smaller test case today. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 as default
On Tue, 5 Jun 2012 20:08:36 +0200 Romain Tartière mentioned: > On Tue, Jun 05, 2012 at 11:01:12AM -0700, Stanislav Sedov wrote: > > Sounds similar. Unfortunately, my app is proprietary. I'll try to > > prepare some smaller test case today. > > Thanks! In the meantime, I am trying to run Banshee with this in > /etc/libmap.conf: > > | [/usr/local/bin/mono] > | libthr.so.3 libpthread.so > Why do you need this? libpthread.so is exactly libthr right now. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 as default
On Tue, 05 Jun 2012 21:14:06 -0400 Steve Wills mentioned: > > From what I saw in your other messages, it sounds like this may be > specific to the use of mono. Or can you reproduce with another program? > Yes, it looks like it can be a mono bug, or unfortunate combination of what mono and ruby do on FreeBSD. I was not able to reproduce this on Linux. I'm still investigating this issue. Hopefully, we'll find out what is it. :) Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Ruby 1.9 as default
On Thu, 07 Jun 2012 20:58:43 +0200 Mel Flynn mentioned: > > Given issues described with swig 1.x earlier on this list, you may want > to investigate if swig 1.x should be removed/patched/whatever before > this sweep. Swig 1.x actually works fine with ruby 1.9, I'm using it quite regularly. SWIG just generate the C source, it does not provide you with include path. It is a responsibility of the application to find out what the correct path are. You can look at my m4 macro as an example of how to do it properly: https://github.com/stass/autoconf-macros/blob/master/ax_ruby_ext.m4 -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: [Solved] ExecJS::RuntimeError in Demo#index
On Tue, 12 Jun 2012 00:14:38 +0300 Златко Асенов mentioned: > Hi All, > > I resolved the issue. > > What I did: > > 1. # pkg_deinstall -r rubygem\* > > Didn't help. > > 2. # portmaster --force-config www/node and unchecked SHARED_V8 option. > > 3. # portmaster devel/ruby-gems > > 4. # gem install rails > > Now it works :) > > If I may ask a question: Is it better to install gems from ports or > using the 'gem install' method? > Personally, I'd recommend using gems (at least for development). This way you will get the updates faster, and will be able to have multiple version of a gem installed, which sometimes is required by some libraries. Also, tools like 'bundle' utilize gems system as well. BTW, you can have gems installed locally for a particular user while having ports managing the system-wide gems. They won't interfere. Just set the GEM_HOME variable to point to a place where you want gems to be installed. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[PATCH]: lang/ruby update to 1.8.7-p370
>Submitter-Id: current-users
>Originator:Stanislav Sedov
>Organization:
>Confidential: no
>Synopsis: [PATCH]: lang/ruby update to 1.8.7-p370
>Severity: non-critical
>Priority: medium
>Category: ports
>Class: update
>Release: FreeBSD 10.0-CURRENT amd64
>Environment:
System: FreeBSD orion.swifttest.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4
r237852M: Sat Jun 30 13:47:41 PDT 2012
s...@orion.swifttest.com:/usr/obj/storage0/home/stas/nsvn/head/sys/ORION amd64
>Description:
This patch updates ruby 1.8 to the latest bugfix release.
>How-To-Repeat:
>Fix:
--- ruby.diff begins here ---
Index: Mk/bsd.ruby.mk
===
RCS file: /home/pcvs/ports/Mk/bsd.ruby.mk,v
retrieving revision 1.218
diff -u -r1.218 bsd.ruby.mk
--- Mk/bsd.ruby.mk 16 May 2012 17:43:28 - 1.218
+++ Mk/bsd.ruby.mk 5 Jul 2012 20:01:14 -
@@ -168,7 +168,7 @@
RUBY_RELVERSION= 1.8.7
RUBY_PORTREVISION= 0
RUBY_PORTEPOCH=1
-RUBY_PATCHLEVEL= 358
+RUBY_PATCHLEVEL= 370
. if ${RUBY_PATCHLEVEL} == 0
RUBY_VERSION?= ${RUBY_RELVERSION}
Index: lang/ruby18/distinfo
===
RCS file: /home/pcvs/ports/lang/ruby18/distinfo,v
retrieving revision 1.76
diff -u -r1.76 distinfo
--- lang/ruby18/distinfo25 Feb 2012 15:25:49 - 1.76
+++ lang/ruby18/distinfo5 Jul 2012 20:01:14 -
@@ -1,2 +1,2 @@
-SHA256 (ruby/ruby-1.8.7-p358.tar.bz2) =
309ccd427e47ef41a70f96462bd3c2ef2e7911ce1b22432ab502f5bc6e949c1b
-SIZE (ruby/ruby-1.8.7-p358.tar.bz2) = 4209883
+SHA256 (ruby/ruby-1.8.7-p370.tar.bz2) =
6359b03a1c8ba16630a96fcb5f972c7af15bd33b752e324cd87964224ab1fe31
+SIZE (ruby/ruby-1.8.7-p370.tar.bz2) = 4211597
--- ruby.diff ends here ---
___
freebsd-ruby@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ruby upgrade compile failing
Hi! Can you, please, send the list of installed ports (ls /var/db/pkg) and the full ruby build log? We have not seen this kind of problem before. Thanks! -- ST4096-RIPE On Jul 18, 2012, at 3:33 AM, H wrote: > > Hi > can you help me with this: > > > ar rcu libruby18-static.a array.o bignum.o class.o compar.o dir.o > dln.o enum.o enumerator.o error.o eval.o file.o gc.o hash.o > inits.o io.o marshal.o math.o numeric.o object.o pack.o parse.o > process.o prec.o random.o range.o re.o regex.o ruby.o signal.o > sprintf.o st.o string.o struct.o time.o util.o variable.o > version.o dmyext.o /usr/local/libexec/ccache/world/cc -I/usr/include > -O -pipe -march=athlon-mp -fPIC-DRUBY_EXPORT -L. -L/usr/lib > -rpath=/usr/lib:/usr/local/lib -pthread -rdynamic -pthread main.o > libruby18-static.a -lcrypt -lm -L/usr/lib > -rpath=/usr/lib:/usr/local/lib -pthread -o miniruby ./miniruby: no > such file to load -- ubygems (LoadError) ./miniruby: no such file to > load -- ubygems (LoadError) /usr/local/libexec/ccache/world/cc -shared > -Wl,-soname,libruby18.so.18 array.o bignum.o class.o compar.o > dir.o dln.o enum.o enumerator.o error.o eval.o file.o gc.o > hash.o inits.o io.o marshal.o math.o numeric.o object.o pack.o > parse.o process.o prec.o random.o range.o re.o regex.o ruby.o > signal.o sprintf.o st.o string.o struct.o time.o util.o > variable.o version.o dmyext.o -lcrypt -lm -L/usr/lib > -rpath=/usr/lib:/usr/local/lib -pthread -o libruby18.so.18 *** > [./.rbconfig.time] Error code 1 ./miniruby: no such file to load -- > ubygems (LoadError) 1 error *** [do-build] Error code 1 > > Stop in /dados/ports/lang/ruby18. > *** [build] Error code 1 > > Stop in /dados/ports/lang/ruby18. > ** Command failed [exit code 1]: /usr/bin/script > -qa /tmp/portupgrade20120718-9886-bv6to7-0 env UPGRADE_TOOL=portupgrade > UPGRADE_PORT=ruby-1.8.7.358,1 UPGRADE_PORT_VER=1.8.7.358,1 make ** Fix > the problem and try again. > > > > # > FreeBSD pop1.hm.net.br 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #1: Wed > Jul 18 05:04:11 BRT 2012 > h...@pop1.hm.net.br:/usr/obj/dados/src/sys/WIPMINI i386 > > > > thanks > Hans > > > > > > -- > > H > +55 11 4249. > > !DSPAM:5006912112481459517921! ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: patching rubygems
On Jul 28, 2012, at 5:28 PM, Steve Wills wrote: > I've done some more work on the issue of patching rubygems and have > produced the attached patch. I'm doing some testing by building all the > rubygem- ports on 9.0 with both 1.9 and 1.8 as default ruby. The build > with ruby 1.9 finished and the patch has only caused issues building the > following ports: > > devel/rubygem-analogger > devel/rubygem-clio > devel/rubygem-rapt > graphics/rubygem-captcha > japanese/rubygem-jpmobile > net-im/rubygem-earthquake > science/rubygem-ai4r > security/rubygem-ezcrypto > www/rubygem-scrubyt > > The batch with ruby 1.9 hasn't finished yet, but I don't expect it to > find many more issues. > > The basic idea is we extract and then build the gem rather than just > installing the built gem. This gives us a chance to patch the gem in > between the extract and build. We could for example change the > dependencies of a port of we know it works with newer version of the > other gems it depends on. This would make updating some gems much easier > and should only make the build time very slightly longer. > > We'd of course want to get an exp-run done before committing this, and > at this point I'm not sure if there's time to get this in before 9.1 or > not, but it would be nice. > > Comments? > Thanks for the patch! I like the idea, though I'm not sure if it makes sense to unpack all the gems we build. Won't it be better to unpack just those gems we have patches for, and use the old code path for gems that do not require patching? Also, I don't really like the "rm -rf $WRKDIR" line. It looks scary. Is it necessary to delete it and create it again? Besides, WRKDIR should probably be quoted, otherwise bad things might happen if it contains spaces (and probably all of the other variables too). Thanks! -- ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: procname when ruby is used
On Wed, 29 Aug 2012 23:06:45 -0400 Steve Wills mentioned: > On 08/29/12 21:38, Doug Barton wrote: > > > > I'm pretty sure you actually want to use command_interpreter instead of > > procname. It should actually be very rare to use procname directly in an > > rc.d script. > > Got it, although that means picking the value at build time, but that > seems OK. > We actually already have a practice of doing that with RUBY_SHEBANG, so it seems reasonable. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: Rubygem_rails is with RUBY 1.8.7, Kindly update it with RUBY 1.9.3
There is already a port for 1.9.3 in the ports tree. Just set the DEFAULT_RUBY_VER to 1.9 in the make.conf before installing the rails. -- ST4096-RIPE On Nov 6, 2012, at 4:13 AM, Syed Hasan Ziaya wrote: > Dear Sir, Greetings, > I have installed Ruby on Rails on FreeBSD9 using rubygem-rails. This > port installs RUBY Version 1.8.7, Kindly update the ports so that it > will install the new Ruby Language i.e. Ruby 1.9.3 > > Ziaya > ___ > freebsd-ruby@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ruby > To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org" > > !DSPAM:5098fed813148620995573! > > ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: More problems than I care to think about
On Nov 15, 2012, at 11:03 AM, Paul Schmehl wrote: > I've been trying to port Snorby to FreeBSD. Emphasis on trying. I run into > problems at every turn, and some seem unresolvable. Snorby requires ruby > 1.9.2 or better. The default version on FreeBSD is 1.8. Putting > RUBY_DEFAULT_VER=1.9 in /etc/make.conf breaks some of the rubygem ports that > will only build on 1.8. > > sysutils/rubygem-bundler was giving me fits. I discovered that while the > port version is 1.1.5, the current version, which fixes the problems I was > having, is 1.2.2. I created a port update for that and was going to submit > it, but then I discovered devel/rubygem-eventmachine "blows up" with a core > dump if built with 1.9. > > This is beyond discouraging and has caused me to abandon the project entirely. > > It seems that we need a massive effort to update ruby and rails and all gems > to the latest versions. Who is responsible for that? How can we get that > done? > All the ruby ports are already at the latest version and we do generally a very good job to keep them updated (and we backport fixes and patches regularly). Rubygems a lot more complicated as there're a lot of messy dependencies between them and a lot of times you cannot just update something because a lot of other stuff that depend on a particular version will break as a result. That's why my recommendation always was to try to keep all gems out of the ports tree unless absolutely necessary. Frankly, it does not make much sense at all to put gems into ports, as gems, unlike ports, support multiple versions being installed, and a lot of ruby software depend on that feature. I don't know what kind of problem you're experiencing with event machine, but I guess it is not ruby related. It'd be helpful if you can post more info. I use eventmachine both from ports and gems for several production application with ruby 1.9 and have not seen any segfaults (except the one that was housed by my own C extension library). -- ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: More problems than I care to think about
On Mon, 19 Nov 2012 14:28:56 -0600 Paul Schmehl mentioned: > --On November 15, 2012 3:59:36 PM -0800 Stanislav Sedov > wrote: > > > > All the ruby ports are already at the latest version and we do generally > > a very good job to keep them updated (and we backport fixes and patches > > regularly). Rubygems a lot more complicated as there're a lot of messy > > dependencies between them and a lot of times you cannot just update > > something because a lot of other stuff that depend on a particular > > version will break as a result. That's why my recommendation always was > > to try to keep all gems out of the ports tree unless absolutely > > necessary. Frankly, it does not make much sense at all to put gems into > > ports, as gems, unlike ports, support multiple versions being installed, > > and a lot of ruby software depend on that feature. > > > > I don't know what kind of problem you're experiencing with event machine, > > but I guess it is not ruby related. It'd be helpful if you can post more > > info. I use eventmachine both from ports and gems for several production > > application with ruby 1.9 and have not seen any segfaults (except the one > > that was housed by my own C extension library). > > > > There isn't anything wrong (that I'm aware of) with the ruby ports, but > ruby-gems are a disaster. They're not up to date, and as you point out > even fixing that wouldn't fix everything that's wrong with them. > > After completely giving up on the port I downloaded the app, downloaded > gems and installed it, ran gem install rails, then went to the directory > where I put the program and ran bundle install. This (supposedly) > downloaded everything I needed to run the app. > > The next step was to create the database by running 'bundle exec rake > snorby:setup'. Rake wasn't installed, so I had to install that. Running > it again gave me an error that libmyslqclient.so.15 was not found. That's > because I'm running 5.5, not 5.0. > > After fixing that, I got another error and that's when I said screw this - > i've got better things to do with my time than beat a damn app into > submission while taking 15 years off my life. > > Gems sucks. Rails sucks. The whole idea is stupid and sucks. > > Someone else will have to do it. I'm done with gems, rails and snorby. > I understand your frustration, I've been there too. Most of the rails/ruby stuff is intended for developers who will have to adjust stuff for their use, and not for end users. Hence a lot of utils in ruby land is optimised for development and not for deployment/delivery. I discovered too that using gems directly through bundle or rbenv or similar is much easier and productive than try to make ports work. This is mostly due to the fact that ports do not support multiple versions of the same gem installed and have no way to support the notion of a "gemset" as well. I should note though, that most gem maintainers are very nice and responsive, so you might consider submitting a patch for the mysql gem upstream that fixes the problem. -- ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/179313: ruby 1.9.3.429 disagrees with bsd.ruby.mk
The following reply was made to PR ports/179313; it has been noted by GNATS. From: Stanislav Sedov To: Garrett Wollman Cc: FreeBSD PR followup Subject: Re: ports/179313: ruby 1.9.3.429 disagrees with bsd.ruby.mk Date: Tue, 4 Jun 2013 16:01:21 -0700 I have never seen this. Are you sure it is not a poudriere bug (which I assume some tool to test a port)? Can you, please, verify that it happens when installing from port as well? Thanks. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: PORTS: converters/ruby-icons (2.0) broken
On Mon, 17 Jun 2013 14:51:41 +0200 Patrick Ernst mentioned: > ===> ruby20-iconv-2.0.0.195,1 depends on file: /usr/local/bin/ruby20 - found > ===> ruby20-iconv-2.0.0.195,1 depends on shared library: iconv.3 - found > ===> Configuring for ruby20-iconv-2.0.0.195,1 > ===> Running extconf.rb to configure > /usr/local/bin/ruby20: No such file or directory -- extconf.rb (LoadError) > *** Error code 1 > > Stop. > make: stopped in /usr/ports/converters/ruby-iconv > > This works with lang/ruby19 but not with lang/ruby20 on FreeBSD 10-CURRENT > It sounds like you set RUBY_DEFAULT_VER to 2.0 when building ruby20 (otherwise you would have /usr/local/bin/ruby20 installed), but not when trying to install ruby-iconv (so it assumes that ruby20 is not the default and looks for ruby20 executable). -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/180246: [patch] lang/ruby20: update to 2.0.0p247
On Jul 8, 2013, at 11:30 PM, Mike Carlson wrote: > The patch I supplied above is not working as I thought... > > The problem seems to be with the lib/mkmf.rb patch, its installing=20 > compiled so' in an invalid location. > > For example, installing databases/rubygem-pg installs the pg_ext.so here:= > > > /usr/local/lib/ruby/gems/2.0/gems/pg-0.15.1/lib/usr/local/lib/ruby/site_r= > uby/2.0/amd64-freebsd9/pg_ext.so > > instead of: > /usr/local/lib/ruby/gems/2.0/gems/pg-0.15.1/lib/pg_ext.so That's weird. Did they change the internal logic of mkmf.rb? -- ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/180246: [patch] lang/ruby20: update to 2.0.0p247
The following reply was made to PR ports/180246; it has been noted by GNATS. From: Stanislav Sedov To: Mike Carlson Cc: "r...@freebsd.org" , "bug-follo...@freebsd.org" Subject: Re: ports/180246: [patch] lang/ruby20: update to 2.0.0p247 Date: Mon, 8 Jul 2013 21:44:27 -0500 On Jul 8, 2013, at 11:30 PM, Mike Carlson wrote: > The patch I supplied above is not working as I thought... > > The problem seems to be with the lib/mkmf.rb patch, its installing=20 > compiled so' in an invalid location. > > For example, installing databases/rubygem-pg installs the pg_ext.so here:= > > > /usr/local/lib/ruby/gems/2.0/gems/pg-0.15.1/lib/usr/local/lib/ruby/site_r= > uby/2.0/amd64-freebsd9/pg_ext.so > > instead of: > /usr/local/lib/ruby/gems/2.0/gems/pg-0.15.1/lib/pg_ext.so That's weird. Did they change the internal logic of mkmf.rb? -- ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: FreeBSD Port: lang/ruby19
On Wed, 14 Aug 2013 15:55:23 -0400 Robert Burmeister mentioned: > FreeBSD 9.2PR2 i386 > > More ports are provoking the error > /usr/local/lib/ruby/site_ruby/1.9/pkgtools.rb:828: stack level too deep > (SystemStackError) > when being updated with portupgrade, > apparently due to the large number of ports that depend on them. > > It takes over half a day to remove and reinstall /math/sage to update > /x11/libx11. > > Please look into this limitation. That's weird. Can you, please, run the following to see how deep the stack goes? Thanks! ruby -e "def iter(acc) puts acc; iter(acc + 1) end; iter(0)" -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: ports/181663: [PATCH] lang/ruby18: mark DEPRECATED and set EXPIRATION_DATE
The following reply was made to PR ports/181663; it has been noted by GNATS. From: Stanislav Sedov To: Yasuhiro KIMURA Cc: FreeBSD PR followup Subject: Re: ports/181663: [PATCH] lang/ruby18: mark DEPRECATED and set EXPIRATION_DATE Date: Thu, 29 Aug 2013 17:15:18 -0700 I am not sure it is a good idea at this point. A lot of commercial consumers of FreeBSD still use ruby 1.8 despite the fact it is EOL, and will use it for a while since some software is quite hard to migrate. I'm all for printing the EOL message, but my believe it is a bit premature to drop ruby 1.8 now or 6 months later. This might cause FreeBSD consumers to drop FreeBSD and move to Linux, which still defaults to 1.8 in it's majority, as far as I know. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Re: fixing port dependencies
On Oct 4, 2013, at 1:17 AM, "Ronald F. Guilmette" wrote: > > > So, um, I just tried to update a bunch of my ports to the latest > revs, which I do rather infrequently, and of course, as usual, > I got a boat load of port build failures. (Sigh.) > > Well, anyway, one of them was this: > > - lang/ruby18 (marked as IGNORE) > > I don't use Ruby myself, so obviously, some other port(s) I have > installed are using it. I've gone ahead and built & installed > lang/ruby20 and that went fine. Now I'd just like to know what, > if anything, I should do, specifically, in order to make every > installed port that I have that was dependent upon ruby18 now > instead dependent upon ruby20. And actually, since we are on > the subject, is doing that exact thing even wise? I have no idea, > but wish I knew. Is it possible that some port or another that I > have installed that was dependent upon ruby18 might now malfunction > if forced to use ruby20 instead? (That notion certainly does not > seem to be entirely out of the question.) Yes, you need to rebuild all ports that depend on ruby18 if you plan to delete it. Ruby libraries are installed in a version-specific location, so only ruby18 will see them (that's also why they have ruby18- prefix). To rebuild all ports that depend on ruby 18 you can use portupgrade: ,-- | portupgrade -x ruby-1.8.\* -fr lang/ruby18 `-- However, I believe the default version of ruby is 1.9 now, so this action will install ruby19 and update all install ruby applications and libraries to use ruby19. If you wish to use ruby20 by default (I do), you should add RUBY_DEFAULT_VER=2.0 to your /etc/make.conf and rebuild ruby20 before performing the aforementioned action. -- ST4096-RIPE signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Time to mark lang/ruby18 DEPRECATED
On Oct 23, 2013, at 4:19 AM, "Akinori MUSHA" wrote: > Great! It's fantastic to see ruby 1.8 finally go. > > Now, why don't we make Ruby 2.0 the default version instead of 1.9? > > Ruby 2.0 is highly (upper) compatible with 1.9 and there should be no > reason to adopt Ruby 1.9.3 by now. Ruby 1.9 is unlikely to have any > more build/platform related change that would expand supported > platforms, architectures or compilers, so I think we should adopt Ruby > 2.0 now that FreeBSD 10 is soon to be shipped with a new compiler and > toolchain that are rapidly evolving. > > What do you guys think? Is there any essential package that does not > run on Ruby 2.0, in which case I could help? At the time we switched to ruby 1.9 there were some ports broken with 2.0 iirc. I'm not sure if the situation changed with the recent wave of 1.8 ports deprecation, though. I agree that we should go with 2.0. Given that new os x ships with 2.0 we definitely want to stay compatible with what people are going to use on OS X. The only major breakages I seen were related to encoding problems (ruby 2.0 uses utf-8 by default). Unfortunately, some of those problems only happen at runtime :-( Do we have a list of ports broken with 2.0 somewhere? -- ST4096-RIPE ___ freebsd-ruby@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
