From: Uri Lublin <uril@redhat.com>
To: Michael Goldish <mgoldish@redhat.com>
Cc: Autotest mailing list <autotest@test.kernel.org>,
KVM mailing list <kvm@vger.kernel.org>
Subject: Re: [Autotest] [RFC] KVM test: Ship rss.exe and finish.exe binaries with KVM test
Date: Thu, 04 Feb 2010 21:13:38 +0200 [thread overview]
Message-ID: <4B6B1C62.8080707@redhat.com> (raw)
In-Reply-To: <987020485.728951265207133506.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
On 02/03/2010 04:25 PM, Michael Goldish wrote:
>
> ----- "Uri Lublin"<uril@redhat.com> wrote:
>
>> On 02/02/2010 01:48 PM, Lucas Meneghel Rodrigues wrote:
>>> Hi folks:
>>>
>>> We're on an effort of streamlining the KVM test experience, by
>> choosing
>>> sane defaults and helper scripts that can overcome the initial
>> barrier
>>> with getting the KVM test running. On one of the conversations I've
>> had
>>> today, we came up with the idea of shipping the compiled windows
>>> programs rss.exe and finish.exe, needed for windows hosts testing.
>>>
>>> Even though rss.exe and finish.exe can be compiled in a fairly
>>> straightforward way using the awesome cross compiling environment
>> with
>>> mingw, there are some obvious limitations to it:
>>>
>>> 1) The cross compiling environment is only available for fedora>=
>> 11.
>>> No other distros I know have it.
>>>
>>> 2) Sometimes it might take time for the user to realize he/she has
>> to
>>> compile the source code under unattended/ folder, and how to do it.
>>>
>>> That person would take a couple of failed attempts scratching
>> his/her
>>> head thinking "what the heck is this deps/finish.exe they're
>> talking
>>> about?". Surely documentation can help, and I am looking at making
>> the
>>> documentation on how to do it more easily discoverable.
>>>
>>> That said, shipping the binaries would make the life of those
>> people
>>> easier, and anyway the binaries work pretty well across all versions
>> of
>>> windows from winxp to win7, they are self contained, with no
>> external
>>> dependencies (they all use the standard win32 API).
>>>
>>> 3) That said we also need a script that can build the entire
>>> winutils.iso without making the user to spend way too much time
>> figuring
>>> out how to do it. I want to work on such a script on the next days.
>>>
>>> So, what are your opinions? Should we ship the binaries or pursue a
>>> script that can build those for the user as soon as the (yet to be
>>> integrated) get_started.py script runs? Remember that the later
>> might
>>> mean users of RHEL<= 5.X and debian like will be left out in the
>> cold.
>>
>> 4) Another option is to make winutils.iso available (somewhere on the
>> web), and
>> download it in get_started.py (similar to other iso images used by kvm
>> test).
>
> But isn't there a legal problem with that?
> winutils.iso contains VLC media player (for the timedrift test).
> If there's no legal problem, this sounds like the best option to me.
You may be right (although I think VLC is GPL).
I meant only for rss.exe and finish.exe.
Other components such as VLC media player can be downloaded separately.
next prev parent reply other threads:[~2010-02-04 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 11:48 [RFC] KVM test: Ship rss.exe and finish.exe binaries with KVM test Lucas Meneghel Rodrigues
2010-02-03 7:53 ` [Autotest] " Yolkfull Chow
2010-02-03 8:56 ` sudhir kumar
2010-02-03 12:09 ` [Autotest] " Uri Lublin
2010-02-03 12:38 ` Lucas Meneghel Rodrigues
2010-02-03 14:25 ` [Autotest] " Michael Goldish
2010-02-04 19:13 ` Uri Lublin [this message]
2010-02-04 19:26 ` Lucas Meneghel Rodrigues
2010-02-04 19:28 ` Lucas Meneghel Rodrigues
2010-02-03 19:04 ` Lucas Meneghel Rodrigues
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B6B1C62.8080707@redhat.com \
--to=uril@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mgoldish@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.