Weird, are you already registered to other mailing lists in rubyforge?
Probably not. But I cannot subscribe to Debian lists either. And they
are all managed by MailMan so there seems to be a pattern.
Well the idea of installer3 is not being used by end-users, but by
developers of Ruby on Windows as "safe bootstrap" that can be
recreated from scratch without huge list of depepdencies to be
manually download, set and everything.
The idea is "Use as much ruby as possible", that means use Rake. We
need some Documentation Love
Well, I consider myself sort of developer but I haven't used Rake so far.
I didn't add one since was playing with the dependencies recipes. I'm
still not convinced this is the best layout for the code, and even
less for the actions I'm performing.
On the original post I commented the task sequence, but since there is
no documentation... :-$
That's why the script would be helpful ;-)
Yeah, Sourcefor servers often timeout, no other alternative than "try
again".
I do not get a download timeout or it is quite well obfuscated at
least. I get slow download of packages one after another and then I
get something like:
execution timed out
rake aborted
I have a exerb "rake.exe" that weights 600K and is the only executable
I need to bootstrap ruby (without requiring a previous ruby
installation). But if you plan to
I installed the OCI but did not do anything to put the ruby bin
directory into my path, and the installer did not do it either. There
must be a zlib1.dll somewhere in your system but there's none in mine.
It is quite common so it might be installed by some other software.
That's because the task sequence is not performed as defined
originally. Can you provide the steps to recreate? maybe a task is
missing the directory as dependency.
Yes, I tried some tasks until I was sure there's nothing that does not
produce any error but it might be that executing the tasks out of
order leaves some fallout.
No, thank you for your time and comments!
Hope you can workaround the mailman issues (or mail directly to
rubyforge staff) and we can collaborate further.
Heh, MailMan is one of the most evil pieces of GNU software out there.
First it used to have broken web templates that rendered the text
nearly invisible for me (and these took years to fix, and even years
after they were fixed upstream they are still common on the web), and
now it refuses to send any email to me. If I was not convinced it is
just because it is a poorly developed piece of buggy code (that nobody
wants to touch, let alone upgrade, fearing it would explode) I would
think it hates me ;-)
OK, I will try to ask at RF.
Thanks
Michal