From curt.hibbs at gmail.com  Tue Oct 18 12:36:09 2005
From: curt.hibbs at gmail.com (Curt Hibbs)
Date: Tue, 18 Oct 2005 11:36:09 -0500
Subject: [Rubyinstaller-devel] Mac OS installer
In-Reply-To: <de63abca0510180018q7d3eb911h7779c75805851486@mail.gmail.com>
References: <227A0497-856F-463C-B7A6-5059EFEA59AE@hexane.org>
	<170fa17805081906004ec57c20@mail.gmail.com>
	<31d15f49050819060779bc713b@mail.gmail.com>
	<31d15f490510170053i7ebe5c5em6119f41ec6b6b7cf@mail.gmail.com>
	<de63abca0510170936t127ea6dew7fda580b245fa598@mail.gmail.com>
	<31d15f490510171224o5d3eb48bk755742a75d3a81f@mail.gmail.com>
	<de63abca0510180018q7d3eb911h7779c75805851486@mail.gmail.com>
Message-ID: <31d15f490510180936v4db7bdaek989a1f547d74821@mail.gmail.com>

I've cc'd this back to the mailing list to keep everyone up to date. I also
cc'd Rich Kilmer because he'd like to see Apple pick this up to be part of
their official distribution, and he has some internal Apple contacts that
could possibly make this a reality.

See the rest of my response below...

On 10/18/05, Mark Hubbart <discordantus at gmail.com> wrote:
>
> On 10/17/05, Curt Hibbs <curt.hibbs at gmail.com> wrote:
> > Don't update for 1.8.3 -- its got bugs in it. Better to stick with 1.8.2
> .
>
> Thanks for the tip. I never updated to 1.8.3 myself, and am glad to
> know that I'm not missing anything :) Still, 1.8.3 comes with an
> entirely different build mechanism for the extensions. If core
> continues to use it for future versions, I'll need to be looking into
> it.


Whenever you're ready to release something based on 1.8.2, let's call it a
preview (or something similar), because Matz will be releasing 1.8.4 at the
end of the year and we'll want to make the official release use 1.8.4.

I worked on the project this evening, to see what still needs to be
> done. I discovered that most of the work ahead is just on features. I
> fixed all but one of the bugs that were slowing me down, so as soon as
> I swat this last one, I think I'll be able to do some sort of a
> release.
>
> This last bug is causing a segmentation fault when rdoc generates
> documentation for installed gems. I'm a bit stymied, but I'll keep
> working on it. C just isn't my thing.
>
> I need to figure out where I can use help on this project... The
> framework code and copious patches might be a bit daunting to someone
> unfamiliar with ruby internals (it's daunting to me), and once I get
> the framework working bug-free, packaging it should be the easy part.


I didn't realize that you had to patch Ruby. What are the nature of these
patches? Are these things that we should submit back for incorporation into
Ruby?

> Also, as I've said, I haven't worked on many collaborative projects
> before, so I'm unsure of how to work this :/


I don't know James or Patrick's skills, but an example could be to help
track down the seg-fault if they were already up to speed.

They could also serve as alpha tester by downloaded and installing what
you've got now. They might run into problems that are easily addressed now
when you'd only have 2 users instead of after the release when there would
be hundreds.

They could also work on incorporating the extensions that we want to bundle.
I advocate keeping it to a minimum, but some just make sense (like RubyGems
and RubyCocoa).

Curt

Anyway, this made me find some time to get some work done on the
> project, so I'll count my blessings :)
>
> cheers,
> Mark
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20051018/b32d901c/attachment.htm

From discordantus at gmail.com  Tue Oct 18 15:20:50 2005
From: discordantus at gmail.com (Mark Hubbart)
Date: Tue, 18 Oct 2005 12:20:50 -0700
Subject: [Rubyinstaller-devel] Mac OS installer
In-Reply-To: <31d15f490510180936v4db7bdaek989a1f547d74821@mail.gmail.com>
References: <227A0497-856F-463C-B7A6-5059EFEA59AE@hexane.org>
	<170fa17805081906004ec57c20@mail.gmail.com>
	<31d15f49050819060779bc713b@mail.gmail.com>
	<31d15f490510170053i7ebe5c5em6119f41ec6b6b7cf@mail.gmail.com>
	<de63abca0510170936t127ea6dew7fda580b245fa598@mail.gmail.com>
	<31d15f490510171224o5d3eb48bk755742a75d3a81f@mail.gmail.com>
	<de63abca0510180018q7d3eb911h7779c75805851486@mail.gmail.com>
	<31d15f490510180936v4db7bdaek989a1f547d74821@mail.gmail.com>
Message-ID: <de63abca0510181220u5288e324neb446e6d7811b218@mail.gmail.com>

On 10/18/05, Curt Hibbs <curt.hibbs at gmail.com> wrote:
> I've cc'd this back to the mailing list to keep everyone up to date. I also
> cc'd Rich Kilmer because he'd like to see Apple pick this up to be part of
> their official distribution, and he has some internal Apple contacts that
> could possibly make this a reality.
>
>  See the rest of my response below...
>
>  On 10/18/05, Mark Hubbart <discordantus at gmail.com> wrote:
> > On 10/17/05, Curt Hibbs <curt.hibbs at gmail.com> wrote:
> > > Don't update for 1.8.3 -- its got bugs in it. Better to stick with
> 1.8.2.
> >
> > Thanks for the tip. I never updated to 1.8.3 myself, and am glad to
> > know that I'm not missing anything :) Still, 1.8.3 comes with an
> > entirely different build mechanism for the extensions. If core
> > continues to use it for future versions, I'll need to be looking into
> > it.
>
>  Whenever you're ready to release something based on 1.8.2, let's call it a
> preview (or something similar), because Matz will be releasing 1.8.4 at the
> end of the year and we'll want to make the official release use 1.8.4.
>
> > I worked on the project this evening, to see what still needs to be
> > done. I discovered that most of the work ahead is just on features. I
> > fixed all but one of the bugs that were slowing me down, so as soon as
> > I swat this last one, I think I'll be able to do some sort of a
> > release.
> >
> > This last bug is causing a segmentation fault when rdoc generates
> > documentation for installed gems. I'm a bit stymied, but I'll keep
> > working on it. C just isn't my thing.
> >
> > I need to figure out where I can use help on this project... The
> > framework code and copious patches might be a bit daunting to someone
> > unfamiliar with ruby internals (it's daunting to me), and once I get
> > the framework working bug-free, packaging it should be the easy part.
>
>  I didn't realize that you had to patch Ruby. What are the nature of these
> patches?

Only one C patch, which adds a RUBY_FRAMEWORK_VERSION constant
alongside RUBY_VERSION et al. The rest are config, makefile and
extconf patches. Ruby itself was *almost* flexible enough to do what
was needed, but not quite. In the future, there may need to be more C
patches, but I'm not sure. Basically, some directories needed to be
moved around, header files relocated, and support for frameworks
added. GNU Readline will be included in the distribution as well, as a
separate framework.

> Are these things that we should submit back for incorporation into
> Ruby?

They aren't clean enough right now, but yes, it would be nice to get
framework build support built in. I'd need to get clean stable patches
that work with the latest 1.8.x version, though.

> > Also, as I've said, I haven't worked on many collaborative projects
> > before, so I'm unsure of how to work this :/
>
>  I don't know James or Patrick's skills, but an example could be to help
> track down the seg-fault if they were already up to speed.
>
>  They could also serve as alpha tester by downloaded and installing what
> you've got now. They might run into problems that are easily addressed now
> when you'd only have 2 users instead of after the release when there would
> be hundreds.

After working on that segfault, I'm not sure I can track it down
myself. I'll work on packaging up what I have, which works pretty well
right now (with a few caveats).

>  They could also work on incorporating the extensions that we want to
> bundle. I advocate keeping it to a minimum, but some just make sense (like
> RubyGems and RubyCocoa).

I agree. I have a version of RubyCocoa that will build against the
framework; RubyGems works, so that opens up a lot of available
extensions.

I'll let you know when I have something (hopefully later this afternoon :)

cheers,
Mark

>  Curt
>
> > Anyway, this made me find some time to get some work done on the
> > project, so I'll count my blessings :)
> >
> > cheers,
> > Mark
> >
>
>


From discordantus at gmail.com  Tue Oct 18 18:55:08 2005
From: discordantus at gmail.com (Mark Hubbart)
Date: Tue, 18 Oct 2005 15:55:08 -0700
Subject: [Rubyinstaller-devel] Mac OS installer
In-Reply-To: <de63abca0510181220u5288e324neb446e6d7811b218@mail.gmail.com>
References: <227A0497-856F-463C-B7A6-5059EFEA59AE@hexane.org>
	<170fa17805081906004ec57c20@mail.gmail.com>
	<31d15f49050819060779bc713b@mail.gmail.com>
	<31d15f490510170053i7ebe5c5em6119f41ec6b6b7cf@mail.gmail.com>
	<de63abca0510170936t127ea6dew7fda580b245fa598@mail.gmail.com>
	<31d15f490510171224o5d3eb48bk755742a75d3a81f@mail.gmail.com>
	<de63abca0510180018q7d3eb911h7779c75805851486@mail.gmail.com>
	<31d15f490510180936v4db7bdaek989a1f547d74821@mail.gmail.com>
	<de63abca0510181220u5288e324neb446e6d7811b218@mail.gmail.com>
Message-ID: <de63abca0510181555l22907e1ci254f2564b8701328@mail.gmail.com>

On 10/18/05, Mark Hubbart <discordantus at gmail.com> wrote:
> I'll let you know when I have something.

The first preview release is posted. You can get it here:
http://homepage.mac.com/discord/Ruby/RubyFramework.pkg.zip

I'll work on some sort of an uninstaller later. For now, refer to the
readme (http://homepage.mac.com/discord/Ruby/FrameworkREADME.rtf) for
information on how this installer backs up Apple's installation.

The general uninstall process would be (shell commands follow):
- configrb -r /usr'
- sudo ruby_orig -e'Dir["/usr/bin/*_orig"].each{|fn|File.rename fn,
fn[/^[^_]*/]}'

...followed by dragging Ruby.framework and Readline.framework to the
trash from /Library/FRameworks, then doing the same to /Library/Ruby.

cheers,
Mark


From curt.hibbs at gmail.com  Tue Oct 18 22:57:37 2005
From: curt.hibbs at gmail.com (Curt Hibbs)
Date: Tue, 18 Oct 2005 21:57:37 -0500
Subject: [Rubyinstaller-devel] Fwd:  Mac OS installer
In-Reply-To: <de63abca0510181559m21c83445x78573934a336cabd@mail.gmail.com>
References: <227A0497-856F-463C-B7A6-5059EFEA59AE@hexane.org>
	<31d15f49050819060779bc713b@mail.gmail.com>
	<31d15f490510170053i7ebe5c5em6119f41ec6b6b7cf@mail.gmail.com>
	<de63abca0510170936t127ea6dew7fda580b245fa598@mail.gmail.com>
	<31d15f490510171224o5d3eb48bk755742a75d3a81f@mail.gmail.com>
	<de63abca0510180018q7d3eb911h7779c75805851486@mail.gmail.com>
	<31d15f490510180936v4db7bdaek989a1f547d74821@mail.gmail.com>
	<de63abca0510181220u5288e324neb446e6d7811b218@mail.gmail.com>
	<de63abca0510181555l22907e1ci254f2564b8701328@mail.gmail.com>
	<de63abca0510181559m21c83445x78573934a336cabd@mail.gmail.com>
Message-ID: <31d15f490510181957n58396145j4b4c8395e454f094@mail.gmail.com>

I think you meant to send this to the list instead of just me, so I've
forwarded it there.

Curt

---------- Forwarded message ----------
From: Mark Hubbart <discordantus at gmail.com>
Date: Oct 18, 2005 5:59 PM
Subject: Re: [Rubyinstaller-devel] Mac OS installer
To: curt at hibbs.com

On 10/18/05, Mark Hubbart <discordantus at gmail.com> wrote:
> On 10/18/05, Mark Hubbart <discordantus at gmail.com> wrote:
> > I'll let you know when I have something.
>
> The first preview release is posted. You can get it here:
> http://homepage.mac.com/discord/Ruby/RubyFramework.pkg.zip

I forgot to mention... There is a lot of important information in the
readme and in the installers opening screens. Be sure to read them
both carefully before installing. The readme is included in the
installer, or you can download it here:
http://homepage.mac.com/discord/Ruby/FrameworkREADME.rtf

cheers,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20051018/acff2375/attachment.htm

From curt.hibbs at gmail.com  Wed Oct 19 11:23:34 2005
From: curt.hibbs at gmail.com (Curt Hibbs)
Date: Wed, 19 Oct 2005 10:23:34 -0500
Subject: [Rubyinstaller-devel] Please test OSX one-click installer
Message-ID: <31d15f490510190823o77ce9916i81adf8ba6d82fed7@mail.gmail.com>

James, Patrick (and anyone else who's interested):

I just wanted to call this out into a separate email thread. Please download
Mark's internal release of the OSX installer, test it, and report any
problems.

This is really exciting!

Curt

---------- Forwarded message ----------
From: Mark Hubbart <discordantus at gmail.com>
Date: Oct 18, 2005 5:59 PM
Subject: Re: [Rubyinstaller-devel] Mac OS installer
To: curt at hibbs.com

On 10/18/05, Mark Hubbart <discordantus at gmail.com> wrote:
>
> The first preview release is posted. You can get it here:
> http://homepage.mac.com/discord/Ruby/RubyFramework.pkg.zip

I forgot to mention... There is a lot of important information in the
readme and in the installers opening screens. Be sure to read them
both carefully before installing. The readme is included in the
installer, or you can download it here:
http://homepage.mac.com/discord/Ruby/FrameworkREADME.rtf

cheers,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20051019/895af347/attachment.htm

From curt.hibbs at gmail.com  Wed Oct 19 11:29:56 2005
From: curt.hibbs at gmail.com (Curt Hibbs)
Date: Wed, 19 Oct 2005 10:29:56 -0500
Subject: [Rubyinstaller-devel] Please test OSX one-click installer
In-Reply-To: <170fa1780510190826v3d0c2f96v3ebbb1acde1996a5@mail.gmail.com>
References: <31d15f490510190823o77ce9916i81adf8ba6d82fed7@mail.gmail.com>
	<170fa1780510190826v3d0c2f96v3ebbb1acde1996a5@mail.gmail.com>
Message-ID: <31d15f490510190829r10e3a4d9k7244f571859f7fe7@mail.gmail.com>

I would think so, but I'll let Mark answer because I'm not an OSX user.

Curt

On 10/19/05, James Stallings II <james.stallings at gmail.com> wrote:
>
> Hi guys,
> Will this impact any currently working installation? do I need to
> uninstall what I have first?
>
> On 10/19/05, Curt Hibbs <curt.hibbs at gmail.com> wrote:
> > James, Patrick (and anyone else who's interested):
> >
> > I just wanted to call this out into a separate email thread. Please
> > download Mark's internal release of the OSX installer, test it, and
> report
> > any problems.
> >
> > This is really exciting!
> >
> > Curt
> >
> > ---------- Forwarded message ----------
> > From: Mark Hubbart <discordantus at gmail.com>
> > Date: Oct 18, 2005 5:59 PM
> > Subject: Re: [Rubyinstaller-devel] Mac OS installer
> > To: curt at hibbs.com
> >
> > On 10/18/05, Mark Hubbart <discordantus at gmail.com> wrote:
> > >
> > > The first preview release is posted. You can get it here:
> > >
> > http://homepage.mac.com/discord/Ruby/RubyFramework.pkg.zip
> >
> > I forgot to mention... There is a lot of important information in the
> > readme and in the installers opening screens. Be sure to read them
> > both carefully before installing. The readme is included in the
> > installer, or you can download it here:
> > http://homepage.mac.com/discord/Ruby/FrameworkREADME.rtf
> >
> > cheers,
> > Mark
> >
>
>
> --
> ===================================
> Woulds't thou so blame
> the fragrant blos'ms wilting
> as never to've had her bloom?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20051019/58e27dc8/attachment-0001.htm

From discordantus at gmail.com  Fri Oct 21 12:59:30 2005
From: discordantus at gmail.com (Mark Hubbart)
Date: Fri, 21 Oct 2005 09:59:30 -0700
Subject: [Rubyinstaller-devel] Mac OS installer
In-Reply-To: <992076E6-0752-4AAA-86A1-35FB0774279C@hexane.org>
References: <227A0497-856F-463C-B7A6-5059EFEA59AE@hexane.org>
	<de63abca0510180018q7d3eb911h7779c75805851486@mail.gmail.com>
	<31d15f490510180936v4db7bdaek989a1f547d74821@mail.gmail.com>
	<de63abca0510181220u5288e324neb446e6d7811b218@mail.gmail.com>
	<de63abca0510181555l22907e1ci254f2564b8701328@mail.gmail.com>
	<de63abca0510181559m21c83445x78573934a336cabd@mail.gmail.com>
	<31d15f490510181959q6a483ddcx942bc65bc91af801@mail.gmail.com>
	<860B395F-136F-469C-9EA4-F5391B948260@hexane.org>
	<de63abca0510191546h7a951a1dtaf4c98c58b6250c5@mail.gmail.com>
	<992076E6-0752-4AAA-86A1-35FB0774279C@hexane.org>
Message-ID: <de63abca0510210959t25ab476btaf0133fdeed528ff@mail.gmail.com>

On 10/21/05, Patrick May <patrick at hexane.org> wrote:
> Mark,
>
> For some reason, I think ruby.h used to be in the archdir:
>
> [glider:~/programming/ruby-web] patsplat% rake compile
> (in /Users/patsplat/programming/ruby-web)
> gcc -F.     -L"/Library/Frameworks/Ruby.framework/Versions/1.8.2/
> Libraries" -I/Library/Frameworks/Ruby.framework/Versions/1.8.2/
> Libraries/Bundles sapi/ruby-web.c -framework Ruby  -lruby -lobjc  -o
> bin/ruby-web
> sapi/ruby-web.c:1:18: error: ruby.h: No such file or directory
> sapi/ruby-web.c: In function 'main':
> sapi/ruby-web.c:13: error: 'ruby_errinfo' undeclared (first use in
> this function)
> sapi/ruby-web.c:13: error: (Each undeclared identifier is reported
> only once
> sapi/ruby-web.c:13: error: for each function it appears in.)
> [glider:~/programming/ruby-web] patsplat%

I'm copying this to the list, since this is an important issue I need
to address. When changing from a traditional dylib to an OSX
framework, it requires some minor changes for software that will be
compiled against it. The quick way to solve the problem is to add args
to CPPFLAGS and LDFLAGS:

to CPPFLAGS, add: -I/Library/Frameworks/Ruby.framework/Headers
to LDFLAGS, add: -framework Ruby

The -framework flag is like the -l flag, but for frameworks. The -I
just adds the proper headers dir. These changes let you use the ruby
framework in the exact same way as a shared library.

cheers,
Mark

> Cheers,
>
> Patrick
>