All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Michael Roth <mdroth@linux.vnet.ibm.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	bsarathy@redhat.com,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	pmyers@redhat.com, agl@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] RFC: Qemu Guest Tools ISO
Date: Thu, 23 Jun 2011 13:31:44 +0200	[thread overview]
Message-ID: <4E032420.5000706@web.de> (raw)
In-Reply-To: <20110623092954.GA2682@bow.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]

On 2011-06-23 11:29, Alon Levy wrote:
>> Implementation:
>>
>> I hope to follow-up in fairly short order with a basic prototype of
>> the tools/workflow to create/install a guest additions ISO. A rough
>> overview of the approach I'm currently pursuing:
>>
>> - Use PyInstaller (built around pye2exe, linux/windows compatible,
>> with logic to pull in required shared libs and windows/tcl/cmd.exe
>> support as needed) to generate executables from python scripts.
>>
>> - Each project exists as a free-form directory with source code, or
>> 32/64 bit pre-compiled binaries, windows-based installers, etc. To
>> add to an ISO a symlink to this directory would be added along with
>> a python installer script which accepts arch/distro as arguments.
>> install/update/uninstall logic handled completely by this install
>> script.
>>
>> - Top-level installer will iterate through guest additions projects
>> and execute installers in turn. (some basic dependency support or
>> explicit ordered may be needed).
> 
> I'm not sure all drivers have installers. sometimes it will need to install
> from inf I think. Should look at how the REHV-M iso does this.

Back in my old days, I wrote a tiny add-on for NSIS to install also
device drivers. Not sure if it still works, but it used to up to XP.
Someone create a wiki page with more information:

http://nsis.sourceforge.net/InstDrv_plug-in

In general, I liked NSIS a lot.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  parent reply	other threads:[~2011-06-23 11:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 18:55 [Qemu-devel] RFC: Qemu Guest Tools ISO Michael Roth
2011-06-23  9:29 ` Alon Levy
2011-06-23 11:08   ` Stefan Hajnoczi
2011-06-23 11:38     ` Daniel P. Berrange
2011-06-23 14:46       ` Michael Roth
2011-06-23 12:00     ` Avi Kivity
2011-06-23 14:54       ` Michael Roth
2011-06-23 15:09         ` Avi Kivity
2011-06-23 15:50           ` Michael Roth
2011-06-23 15:25       ` Anthony Liguori
2011-06-23 15:52         ` Avi Kivity
2011-06-27  0:24           ` Natalia Portillo
2011-06-23 11:31   ` Jan Kiszka [this message]
2011-06-23 14:41   ` Michael Roth
2011-06-23 11:14 ` Ronen Hod

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=4E032420.5000706@web.de \
    --to=jan.kiszka@web.de \
    --cc=agl@linux.vnet.ibm.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=bsarathy@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pmyers@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.