Thanks Rainer,
I'm trying to make ruby_select.
On Tue, 03 Aug 2010 15:59:55 +0200, Rainer Müller wrote:
> On 2010-08-02 18:46 , David Baumgold wrote:
>> I'm fine with all of that. Kimura, do you want to be the maintainer of the
>> ruby_select port? Ryan, can you instruc
On 2010-08-02 18:46 , David Baumgold wrote:
> I'm fine with all of that. Kimura, do you want to be the maintainer of the
> ruby_select port? Ryan, can you instruct us on the proper way to write a
> select port, now that the select functionality is built into Macports?
Just
On Aug 2, 2010, at 11:46, David Baumgold wrote:
> Ryan, can you instruct us on the proper way to write a select port, now that
> the select functionality is built into Macports?
I'm afraid I haven't looked into it, I just remember hearing on the list about
its existence.
I'm fine with all of that. Kimura, do you want to be the maintainer of the
ruby_select port? Ryan, can you instruct us on the proper way to write a
select port, now that the select functionality is built into Macports?
On Mon, Aug 2, 2010 at 10:18 AM, kimura wataru wrote:
> Hi all,
>
ruby" port (Ruby
> version 1.8), rather than the "ruby1.9" executable from the "ruby19" port
> (Ruby version 1.9). With the Python ports, users can select default versions
> using the "python_select" port -- it would make a lot of sense to do the
> same thing f
the "python_select" port -- it would make a lot of sense to do the same
> thing for Ruby using a "ruby_select" port, but sadly, that port doesn't
> currently exist. There is a +nosuffix variant for the current "ruby19" port,
> but this is not a good solut
the "ruby" port (Ruby
version 1.8), rather than the "ruby1.9" executable from the "ruby19" port
(Ruby version 1.9). With the Python ports, users can select default versions
using the "python_select" port -- it would make a lot of sense to do the
same thing fo
