Re: Fwd: Plans for GTK+ Bundles for win32 and =?UTF-8?Q?win=36=34=3F?=
- From: dieterv <dieterv optionexplicit be>
- To: John Stowers <john stowers lists gmail com>
- Cc: gtk-devel-list gnome org
- Subject: Re: Fwd: Plans for GTK+ Bundles for win32 and win64?
- Date: Thu, 08 Sep 2011 15:20:28 +0200
On Fri, 09 Sep 2011 00:12:09 +1200, John Stowers wrote:
It takes a "build description" file like:
https://github.com/dieterv/pygtk-installer/blob/master/wix/2.24.0.win32.xml
downloads required files, extracts them, applies transformations if
requested,
repacks, etc until finally a .msi is produced.
It is currently capable of packaging zips from ftp.gnome.org and
also
Python
distutils generated .msi files (for PyCairo, PyGTK, PyGObject, etc).
Cleaning this up and making it more generic and easier to use is
something
I've been wanting to do for a long time now...
Cool!
note: these are my uninformed ideas, I have not actually seen the
implementation for the methods you describe...
I think JHBuild is *almost* able to do this itself. If the binary/zip
module type patch was applied to JHbuild then I think this would not
be
too much work to complete.
Wasn't the binary/zip module type patch rejected some time ago? Or
maybe
not rejected perse, maybe there was just a heated discussion around
it, I don't remember. Anyway, personally, I'd prefer to have separate
a) build tool and b) packaging tool. The intermediate format doesn't
matter much (zip, msi, rpm, ...).
AIUI JHbuild now tracks installed files and can create a manifest.
This
manifest + JHbuild supporting binary/zip module types would give you
all
the meta information to write msi/wix/nsi installers.
Looks like I have some studying to do :)
Thanks!
Dieter
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]