On Tue, 05 Jun 2012 21:14:06 -0400
Steve Wills swi...@freebsd.org 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
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as broken in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
On 2-6-2012 3:32, Steve Wills wrote:
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.
This may become obsolete soon, since graphics/gdal
On Thu, 07 Jun 2012 20:58:43 +0200
Mel Flynn rfl...@acsalaska.net 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
On Jun 7, 2012, at 2:58 PM, Mel Flynn rfl...@acsalaska.net wrote:
On 2-6-2012 3:32, Steve Wills wrote:
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
Synopsis: [MAINTAINER UPDATE] sysutils/rubygem-bundler: update to version 1.1.4
Responsible-Changed-From-To: freebsd-ports-bugs-ruby
Responsible-Changed-By: edwin
Responsible-Changed-When: Thu Jun 7 23:35:36 UTC 2012
Responsible-Changed-Why:
ruby@ wants this port PRs (via the GNATS Auto Assign
On 06/07/12 17:57, Steve Wills wrote:
This is expected. Try setting RUBY_DEFAULT_VER instead.
I probably should have been more clear about this. The ruby ports only
create ${PREFIX}/bin/ruby for the default ruby. So if you have ruby 1.9
installed but it is not the default ruby, you won't
