Rubyinstaller devel - Nov 2004 - a simple ruby build script for macos x

Hi, all

I think this is where I should send this...

Attached is my basic build script. As I said, it only *builds* ruby,
oniguruma, and readline at the moment. I cleaned up the code a little,
and added a few more comments, but basically what you see is what you
get, for now. It''s a starting point.

Let me know what you think. I''ll be working on it some more tonight,
and over the next couple days when I get a chance. It wants some
serious refactoring.

cheers,
Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build-all.rb
Type: application/octet-stream
Size: 3112 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20041105/3989d67b/build-all.obj

Mark Hubbart wrote:
>
> Hi, all
>
> I think this is where I should send this...
>
> Attached is my basic build script. As I said, it only *builds* ruby,
> oniguruma, and readline at the moment. I cleaned up the code a little,
> and added a few more comments, but basically what you see is what you
> get, for now. It''s a starting point.
>
> Let me know what you think. I''ll be working on it some more
tonight,
> and over the next couple days when I get a chance. It wants some
> serious refactoring.
Thanks, Mark!

For the rest of you on the ML, let me bring you up-to-date with the latest
happenings (there have been a bunch a private emails that preceded this
posting by Mark).

Independently of the one-click installer project, Mark has produced a mac
osx installer, and recently announced a new release of it on the
ruby-talk-ML. I contacted Mark off-list and asked him if he would like to
join forces with our mac osx effort being headed up by Steve Steiner.

Both Mark and Steve liked the prospect of sharing the work (who
wouldn''t...
we all have outside lives to live as well :-)! And we all like the idea of
getting a headstart by using what Mark has already done.

Mark did caution us that what he has is still a little rough around the
edges (but, so what? even the build system for the window''s installer
could
still use some improvements).

I made Steve an Admin on the one-click installer project so that he can help
share in the administration of the project itself (for things like granting
cvs commit access). And he is going to setup some pages on our wiki to help
guide and document the mac os x effort.

Note to Mark: As I told Steve when he first signed on for the mac os x
effort, I think you''ll find this project to be personally very
gratifying.
If you look at the download stats on RubyForge, you''ll see that
one-click
installer for windows has been wildly popular -- about 150 downloads a day,
and over 21,000 total downloads since the installer was moved to RubyForge a
year ago!

I want to duplicate this success on the mac. Making it easy for people to
install and get started on Ruby is one of the primary ways we can help
spread Ruby adoption in the industry!

Now I just need to find someone to do the kde and gnome versions of the
installer and we''ll be set. If you know anyone who might be interested,
please send them my way.

Curt

I haven''t got a copy of the script in question and have some time to 
work on this this week.

Steve

On Nov 5, 2004, at 3:17 PM, Curt Hibbs wrote:
> Mark Hubbart wrote:
>>
>> Hi, all
>>
>> I think this is where I should send this...
>>
>> Attached is my basic build script. As I said, it only *builds* ruby,
>> oniguruma, and readline at the moment. I cleaned up the code a little,
>> and added a few more comments, but basically what you see is what you
>> get, for now. It''s a starting point.
>>
>> Let me know what you think. I''ll be working on it some more
tonight,
>> and over the next couple days when I get a chance. It wants some
>> serious refactoring.
>
> Thanks, Mark!
>
> For the rest of you on the ML, let me bring you up-to-date with the 
> latest
> happenings (there have been a bunch a private emails that preceded this
> posting by Mark).
>
> Independently of the one-click installer project, Mark has produced a 
> mac
> osx installer, and recently announced a new release of it on the
> ruby-talk-ML. I contacted Mark off-list and asked him if he would like 
> to
> join forces with our mac osx effort being headed up by Steve Steiner.
>
> Both Mark and Steve liked the prospect of sharing the work (who 
> wouldn''t...
> we all have outside lives to live as well :-)! And we all like the 
> idea of
> getting a headstart by using what Mark has already done.
>
> Mark did caution us that what he has is still a little rough around the
> edges (but, so what? even the build system for the window''s
installer
> could
> still use some improvements).
>
> I made Steve an Admin on the one-click installer project so that he 
> can help
> share in the administration of the project itself (for things like 
> granting
> cvs commit access). And he is going to setup some pages on our wiki to 
> help
> guide and document the mac os x effort.
>
> Note to Mark: As I told Steve when he first signed on for the mac os x
> effort, I think you''ll find this project to be personally very 
> gratifying.
> If you look at the download stats on RubyForge, you''ll see that 
> one-click
> installer for windows has been wildly popular -- about 150 downloads a 
> day,
> and over 21,000 total downloads since the installer was moved to 
> RubyForge a
> year ago!
>
> I want to duplicate this success on the mac. Making it easy for people 
> to
> install and get started on Ruby is one of the primary ways we can help
> spread Ruby adoption in the industry!
>
> Now I just need to find someone to do the kde and gnome versions of the
> installer and we''ll be set. If you know anyone who might be
interested,
> please send them my way.
>
> Curt
>
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>

Ok, so the messages came in in the wrong order...I''m an idiot.

Sorry.

Steve

On Nov 14, 2004, at 8:07 PM, Steve Steiner wrote:
> I haven''t got a copy of the script in question and have some time
to
> work on this this week.
>
> Steve
>
> On Nov 5, 2004, at 3:17 PM, Curt Hibbs wrote:
>
>> Mark Hubbart wrote:
>>>
>>> Hi, all
>>>
>>> I think this is where I should send this...
>>>
>>> Attached is my basic build script. As I said, it only *builds*
ruby,
>>> oniguruma, and readline at the moment. I cleaned up the code a 
>>> little,
>>> and added a few more comments, but basically what you see is what
you
>>> get, for now. It''s a starting point.
>>>
>>> Let me know what you think. I''ll be working on it some
more tonight,
>>> and over the next couple days when I get a chance. It wants some
>>> serious refactoring.
>>
>> Thanks, Mark!
>>
>> For the rest of you on the ML, let me bring you up-to-date with the 
>> latest
>> happenings (there have been a bunch a private emails that preceded 
>> this
>> posting by Mark).
>>
>> Independently of the one-click installer project, Mark has produced a 
>> mac
>> osx installer, and recently announced a new release of it on the
>> ruby-talk-ML. I contacted Mark off-list and asked him if he would 
>> like to
>> join forces with our mac osx effort being headed up by Steve Steiner.
>>
>> Both Mark and Steve liked the prospect of sharing the work (who 
>> wouldn''t...
>> we all have outside lives to live as well :-)! And we all like the 
>> idea of
>> getting a headstart by using what Mark has already done.
>>
>> Mark did caution us that what he has is still a little rough around 
>> the
>> edges (but, so what? even the build system for the window''s
installer
>> could
>> still use some improvements).
>>
>> I made Steve an Admin on the one-click installer project so that he 
>> can help
>> share in the administration of the project itself (for things like 
>> granting
>> cvs commit access). And he is going to setup some pages on our wiki 
>> to help
>> guide and document the mac os x effort.
>>
>> Note to Mark: As I told Steve when he first signed on for the mac os x
>> effort, I think you''ll find this project to be personally very
>> gratifying.
>> If you look at the download stats on RubyForge, you''ll see
that
>> one-click
>> installer for windows has been wildly popular -- about 150 downloads 
>> a day,
>> and over 21,000 total downloads since the installer was moved to 
>> RubyForge a
>> year ago!
>>
>> I want to duplicate this success on the mac. Making it easy for 
>> people to
>> install and get started on Ruby is one of the primary ways we can help
>> spread Ruby adoption in the industry!
>>
>> Now I just need to find someone to do the kde and gnome versions of 
>> the
>> installer and we''ll be set. If you know anyone who might be 
>> interested,
>> please send them my way.
>>
>> Curt
>>
>> _______________________________________________
>> Rubyinstaller-devel mailing list
>> Rubyinstaller-devel@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>>
>
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>

Mark,

	Thanks!

	Where it says:

	# By hand from now on, at the moment.
	
	What exactly do you do from there on out?  I''d like to plan the 
automation of that part, too.

Steve



On Nov 5, 2004, at 3:15 AM, Mark Hubbart wrote:
> Hi, all
>
> I think this is where I should send this...
>
> Attached is my basic build script. As I said, it only *builds* ruby,
> oniguruma, and readline at the moment. I cleaned up the code a little,
> and added a few more comments, but basically what you see is what you
> get, for now. It''s a starting point.
>
> Let me know what you think. I''ll be working on it some more
tonight,
> and over the next couple days when I get a chance. It wants some
> serious refactoring.
>
> cheers,
> Mark
> <build-all.rb>_______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel

Hi,

On Sun, 14 Nov 2004 20:14:02 -0500, Steve Steiner <ssteiner@mac.com>
wrote:
> Mark,
> 
>         Thanks!
> 
>         Where it says:
> 
>         # By hand from now on, at the moment.
> 
>         What exactly do you do from there on out?  I''d like to
plan the
> automation of that part, too.
When the automated part was finished, I had two directories, one that
held copies of all the installed readline files, and one that held all
the readline files and all the ruby files. For the recent package I
made, here are the basic steps that were needed to finish the process,
after the automated part was done: (more details below)

1. Remove any readline files from the ruby directory; move the
''readline.bundle'' into the readline tree.
2. Using the GUI PackageMaker program
(/Developer/Applications/Utilities), create basic packages.
3. Use PackageMaker to create one meta-package for the two normal packages.
4. Put the packages in a folder with the meta-package, throw in the
sample code from the source tree.
5. Use DiskUtility to create a read/write disk image from that folder,
then set icon positions, background images, window size, etc. from the
Finder. Use DiskUtility to convert the read/write disk image to a
read-only compressed image.

Step one was fairly simple to solve. Since the release, I wrote up a
simple class to handle moving the files to the right place, based on
snapshots taken between installs.

Step two shouldn''t be too much of a problem, the PackageMaker util can
be called from the command line, and you can pass all the necessary
filenames as arguments. Type
`/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
--help` to get the list of arguments required.

Step three might be more hairy; I can''t see that there''s a cli
way to
have PackageMaker create the metapackages. It may come down to
"hand-building" them, using several separate tools to create the
correct format. I haven''t looked into this much yet; but I know there
*is* a solution, I''m just not sure how much work will be involved.

Step four is just moving around the files, no problem. Copying out the
sample code will require special cases, though, since not all the
sample code is in the standard locations. Copying the sample code is
not a vital step, but some of those who emailed me mentioned how nice
it was to have all the sample code there in one place for them to
peruse. Still, that step is simple.

Step five; All the disk image creation and conversion is dead simple,
using `hdiutil`. Setting icon positions and background images might be
more difficult, though. I realize the importance of the presentation
is debatable, though, and it is the least important item on the list,
afaic.

So that''s about it. Any questions, just ask.

cheers,
Mark