Hello, I''m working on packaging http://www.ruby-web.org. On Windows, I am depending on the One Click Installer. This not only provides ruby, but a host of other useful things like DBI. I''d like to provide the same functionality on the Mac. What is the status of the Mac OS X installer? Is this a project which could / should be picked up? Cheers, ~ Patrick
I''m interested in this as well. I''d love to see a package similar to the one for windows, which has been a godsend when deploying for that platform. I''d like to get involved in whatever capacity is most helpful. Twitch On 8/18/05, Patrick May <patrick@hexane.org> wrote:> Hello, > > I''m working on packaging http://www.ruby-web.org. On Windows, I am > depending on the One Click Installer. This not only provides ruby, > but a host of other useful things like DBI. I''d like to provide the > same functionality on the Mac. > > What is the status of the Mac OS X installer? Is this a project > which could / should be picked up? > > Cheers, > > ~ Patrick > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel >-- ==================================Woulds''t thou so blame the fragrant blos''ms wilting as never to''ve had her bloom?
Mark Hubbart has an almost-ready-to-release alpha version of the one-click installer for OSX. I''ll let him respond as to what kind of help would be useful. Curt On 8/19/05, James Stallings II <james.stallings@gmail.com> wrote:> I''m interested in this as well. I''d love to see a package similar to > the one for windows, which has been a godsend when deploying for that > platform. > > I''d like to get involved in whatever capacity is most helpful. > > Twitch > > On 8/18/05, Patrick May <patrick@hexane.org> wrote: > > Hello, > > > > I''m working on packaging http://www.ruby-web.org. On Windows, I am > > depending on the One Click Installer. This not only provides ruby, > > but a host of other useful things like DBI. I''d like to provide the > > same functionality on the Mac. > > > > What is the status of the Mac OS X installer? Is this a project > > which could / should be picked up? > > > > Cheers, > > > > ~ Patrick > > _______________________________________________ > > Rubyinstaller-devel mailing list > > Rubyinstaller-devel@rubyforge.org > > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel > > > > > -- > ==================================> Woulds''t thou so blame > the fragrant blos''ms wilting > as never to''ve had her bloom? > > _______________________________________________ > Rubyinstaller-devel mailing list > Rubyinstaller-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/rubyinstaller-devel >
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
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 > > > >
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
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.zipI 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
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 >