From: Grobian <grobian@gentoo.org>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Ruby issue
Date: Fri, 07 Oct 2005 08:04:16 +0200 [thread overview]
Message-ID: <43460FE0.8010700@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0510071155470.3258@loopy.telegraphics.com.au>
Finn Thain wrote:
>
> On Thu, 6 Oct 2005, Grobian wrote:
>> A short situation sketch:
>> - ruby 1.8.2 compiles with some patches made by usata on Panther
>> - ruby 1.8.2 collides on Tiger with system installed ruby
>> - ruby 1.8.2 contains security vulnerability and stuff
>> - ruby 1.8.3 is safe(r)
>> - ruby 1.8.3 doesn't compile on Panther due to autoconf 2.59 requirement
>
> Can the appropriate autoconf be added to the base system?
No, because it collides with the system installed one. For progressive
people this shouldn't be a problem at all.
--
Fabian Groffen
Gentoo for Mac OS X Project -- Interim Lead
--
gentoo-osx@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-07 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 20:30 [gentoo-osx] Ruby issue Grobian
2005-10-07 2:01 ` Finn Thain
2005-10-07 6:04 ` Grobian [this message]
2005-10-08 15:01 ` Grobian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43460FE0.8010700@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-osx@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox