David,
I will be really happy to take on this task. I think the Ruby Gem
which is not available on windows is the logging component currently used
by DC. If we fall back to the commonly available gem, then we should be ok,
but that means a lot of code changes possible.
Thanks.
Tong Li
Emerging Technologies & Standards
Building 501/B205
[email protected]
From: David Lutterkort <[email protected]>
To: [email protected]
Date: 01/12/2012 12:37 PM
Subject: Re: Issues with the delta cloud env setup
On Thu, 2012-01-12 at 09:12 -0500, Tong Li wrote:
> There are also elements which are not available on windows. I went down
the
> same path as my dev env are on windows, had quite few days digging and
> pounding my fists against the desk and eventually switched to Ubuntu
which
> is a lot simpler. Unless we are serious about supporting windows and put
> some efforts including careful selecting dependent Ruby gems, we will
have
> people continue wanting run or develop on windows and having issues. Just
> my 2 cents. Thanks.
I am all for making it possible to run and hack Deltacloud on Windows -
I simply do not have a single Windows machine available where I could
try that myself. But I am more than happy to accept patches to that end.
Do you still have any notes about what issues you ran into with your
Windows setup ? At this point, it would take some enterprising soul to
slog to the issues one-by-one and either document workarounds or fix
them.
As for the thin issue that the OP had: that's a design issue with
rubygems, in that it doesn't distinguish between source and binary
packages (with a sane package mgr, you install binary packages, so that
you do not need a whole build env just to install)
I believe that the best 'fix' for the thin issue is to carefully
document setup under Windows.
David
