Collecting list of gems and projects

Hello fellow developers,

It seems the post at RubyInside [1] generated quite a
reaction, rest
assured that One-Click Installer will not be dead, but we
should shake
the ground and put new blood in it.

For that job, the move to MinGW was the best looking
alternative I
found. Even after the negative comments and the lack of
feedback and
general troubleshooting from the community, we moved
forward.

What's our plan? (you may ask).

Right now the idea is play with the generated sandboxed ruby
(from now
own installer3 ruby) and find something that wouldn't work.
Since
there aren't too many things out there that will work out of
the box.

Tip: For those who don't know where to get the sandbox, look
here [2]

Our list of priorities:

- Move the work being done in the Bazaar repository to
Subversion

I know bzr is not spread like git among developers, but is
not so
complex to use. In any case, I'll push updates into
rubyinstaller svn
repository and allow integration from it, so developers
familiar with
subversion can work with us :-D

- Provide a simple One-Click Installer "Developer
Kit"

This is almost done, since you can right now grab the
generated
sandboxed MinGW and MSYS installation (using the installer3
recipes),
add it to your PATH and you're done. What it misses right
now is a
proper Windows Installer and the creation of some shortcuts
for the
standard console and other to start the MSYS (Bash)
console.

This will make it more easy for developers and users to
install and
use gems that requires a compiler and that will not be
"prepared" for
MinGW. Read the next point about this.

- Improve compatibility of existing gems.

Ruby on Windows definition is shared among three platforms
(RUBY_PLATFORMS), i386-mswin32 (VC), i386-mingw32 (MinGW)
and last,
but not least i386-cygwin. The later ships with is own
compiler, so
mixing environments with that will only make your head
hurts.

Regarding the other two platforms, a lot of projects uses
regexp
(regular expressions) to determine "if you are running
on Windows".
Some of them only consider 'win32', which will leave mingw32
and even
x64 version of Ruby out of the equation.

I even see others that look for 'win' and mark it as
Windows... wrong!
Ruby for OSX also fall into this category (darwin?).

So, since I can't work on projects I don't use on a daily
basis, I
encourage everybody list the gems and extensions that cannot
run out
of the box with the tools provided by the Developer Kit and
the
Installer3 Ruby.

I'll try to add them to our CI and provide the patches
needed to fix
most of the situations with them, but will require also
original
developers merge them and start providing releases for it.

So, where we are right now.

RubyGems 1.1.0 is out, which is compatible with this new
Installer3 Ruby.

I've in my list, ordered by priority:

Mongrel
sqlite3-ruby
mysql
win32console
rspec

Please share with me your gems that don't work out of the
box either
because there is no pre-compiled gem (and it requires
special
libraries) or because it looks wrongly for the
RUBY_PLATFORM.

Just open a Integration Request (Support and Continuous
Integration
Requests) tracker at RubyForge [3], provide project name,
repository
url, category of usage (ui, console, database, testing,
etc.) and
comments regarding your problems with it.

Thanks everybody for your support, your mails and your
comments either
in RubyInside, directly to my inbox, IM or IRC.

[1] http://www.rubyinside.com/is-window
s-a-first-class-platform-for-ruby-823.html
[2] http://groups.google.com/g
roup/comp.lang.ruby/browse_frm/thread/1e2f1b9a3d611e3b?tvc=1

[3] http://rubyforge.org/tracker/?atid=2289
5&group_id=167&func=browse

Regards,
-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to
learn from
the experience of others, are also remarkable for their
apparent
disinclination to do so.
Douglas Adams
_______________________________________________
Rubyinstaller-devel mailing list
Rubyinstaller-develrubyforge.org
http://rubyforge.org/mailman/listinfo/rubyinstaller-dev
el

Luis,

I'm really glad to see this is gaining momentum.

As far as gems go, I think Hoe would be a good candidate to
work on.
I tested it, and it has some problems.  I think all it needs
is a fix
to the regex in a few places.  I'll take a closer look soon.
 I was
able to compile, package and install the win32console gem
into my
sandbox.  From some early tests, it seems to work just fine.
 I don't
have time tonight, but if you're interested, I'll put some
notes
together on what I did.

I also have some questions about rake tasks, and maybe some
ideas
about new ones.  I want to be able to clobber the sandbox,
without
clobbering the downloads.  Is this currently possible?  If
not, how
about splitting these into two tasks?  Something like this
(pseudocode):

namespace(:clobber) do
  namespace(:sandbox) do
    #clobber sandbox
  end

  namespace(:downloads) do
    #clobber sandbox
  end

 end

 task :clobber   => ['clobber:sandbox',
'clobber:downloads']

Thanks,

Gordon
_______________________________________________
Rubyinstaller-devel mailing list
Rubyinstaller-develrubyforge.org
http://rubyforge.org/mailman/listinfo/rubyinstaller-dev
el

On Sat, Mar 29, 2008 at 7:17 PM, Gordon Thiesfeld
<gthiesfeldgmail.com> wrote:
> Luis,
>
>  I'm really glad to see this is gaining momentum.
>
>  As far as gems go, I think Hoe would be a good
candidate to work on.
>  I tested it, and it has some problems.  I think all it
needs is a fix
>  to the regex in a few places.  I'll take a closer look
soon.  I was
>  able to compile, package and install the win32console
gem into my
>  sandbox.  From some early tests, it seems to work just
fine.  I don't
>  have time tonight, but if you're interested, I'll put
some notes
>  together on what I did.
>

Hehehe, I was the responsible for the Hoe patches, so blame
me :-P

I didn't listed Hoe or RubyInline (and ParseTree) --- yet


>  I also have some questions about rake tasks, and maybe
some ideas
>  about new ones.  I want to be able to clobber the
sandbox, without
>  clobbering the downloads.  Is this currently possible?
 If not, how
>  about splitting these into two tasks?  Something like
this
>  (pseudocode):
>

yes: rake clean
that will "clean" your sandbox and let you be
ready to extract,
prepare, configure and compile! 

clobber will just wip your downloads folder :-D

>
>  Thanks,
>

No problem, is good to have "echo" to my messages
:-D

Regards,
-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to
learn from
the experience of others, are also remarkable for their
apparent
disinclination to do so.
Douglas Adams
_______________________________________________
Rubyinstaller-devel mailing list
Rubyinstaller-develrubyforge.org
http://rubyforge.org/mailman/listinfo/rubyinstaller-dev
el