Re: [DebianGIS] Should osgeo4w be included in the FOSS4G2008 live CD?
Hello live DVD builders,
(others can ignore this, no Debian content here sorry)
FYI, responses from the MacOSX & MS-Windows packagers of QGIS and GRASS
re. courtesy installers for other OSes included on the live DVD.
As a matter of need they package most of the dependency stack as well.
Low bandwidth here means that I can not personally checkout & reupload
a 1.5gb .iso. I am happy to work on control scripts and such.
Hamish
-----------------------------------------
From: William Kyngesburye
On Sep 16, 2008, at 9:00 AM, Hamish wrote:
>>> Cameron wrote:
>> 1. Is the software linked below stable and production ready now, with
>> no testing required?
>
> Yes.
> (cc to William & Marco for their thoughts)
>
The main problem I keep having is the Postgres install doesn't always
initialize and may require the user to manually run initdb.
Otherwise, everything has been stable.
>> 2. How much space does it take up? (I'm not sure how much space we
>> have
>> left on the image. One of the techies might be able to answer this)
>
> (William/Marco?)
>
I use separate Tiger (10.4) and Leopard (10.5) binaries, and include
both 32bit and 64bit for Leopard, so it adds up quickly for OSX.
There are also some outside dependencies needed, like Python.
Frameworks (the core, like fwtools): 55MB
GRASS 6.3: 49MB
MapServer 5.2: 9MB
Qgis 0.11: 86MB
Postgres 8.3: 34MB
PostGIS 1.3.3: 1.5MB
pgRouting: 2MB
PHP5: 35MB (I don't use the system PHP for mapscript)
If you're OK with ECW and MrSID licenses, the ECW and MrSID plugins
for GDAL are an extra 6MB.
Deps not on my site:
Python (for Tiger): 18.5MB
NumPy (for Tiger): 3.5MB (the older binaries have disappeared from the
download site, so I can dig up mine from a backup - I haven't updated
GDAL for the latest numpy yet)
wxPython: 35MB (experimental for GRASS 6.3, so could be left out)
>> If so, then we might be able to get it on the disk. But as I don't
>> have
>> experience with these tools I'd be hesitant to include them
>> (because of
>> our short timeline) without hearing a strong chorus of support from
>> existing packaging techies.
>
> I would have no hesitation in including FWTools, native GRASS and QGIS
> packages for MS-Windows by Marco, and William's packages for the
> Mac. I
> think it would be a crying shame for them not to be there actually.
>
> Again, I am asking for nothing more that a directory on it like
>
> /installers/windows/*.exe
> /installers/macosx/*.dmg
> /installers/readme.html
>
Since there are a lot of packages for OSX, I could suggest a directory
organization that would show the order that some need to be installed
in.
> To be honest I don't spend much time on the Mac and even less with MS
> but I have been in the direct line of fire for feedback for a long
> time,
> and the recent feedback has been very good.
>
When I was at last year's conference (sorry, can't make it this year)
I was pleasantly surprised to get a lot of positive comments from Mac
users AND developers (and I saw a lot of MacBooks).
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
-----------------------------------------
From: Marco Pasetti
Hi all,
actually the current GRASS and QGIS binary releases are not integrated into
the osgeo4w installer. This mainly because the official release of GDAL for
MS-Windows (and all the related tools included in FWTools for Windows) are
built using MSVC, while the current GRASS and QGIS binaries are built using
MinGW/MSYS; this means that the latters cannot link to the osgeo4w MSVC
built dependencies, so I needed to produce an independent binary release for
both (QGIS could easily link to osgeo4w MSVC built dependencies, if built
with MSVC, but since it needs GRASS, and GRASS needs MinGW built deps, it
still needs to be built with MinGW too).
This said, I'll try to reply, but talking about the official independent
binary releases of both GRASS and QGIS for MS-Windows:
>>> 1. Is the software linked below stable and production ready now, with
>>> no testing required?
GRASS: yes, but with some reserves;
I wrote almost all about the WinGRASS project (missing modules, know bugs,
optionally supported features and formats, to-do list, installer usage....)
into the following document:
http://grass.osgeo.org/grass63/binary/mswindows/native/README.html
QGIS: yes. The differences with the other builds (for Mac and Linux) are
only on the lack of support for some formats (such as: ECW, OGDI,
MySQL....); that depends on the building environment --> see
http://grass.osgeo.org/wiki/WinGRASS_Current_Status#Dependencies for details
>>> 2. How much space does it take up?
GRASS Installer: 44,3 MB
GRASS Installed: 145 MB
QGIS Installer: 73,8 MB
GRASS Installed: 225 MB
please, note that QGIS contains quite all GRASS. Thanks to MS DLL hell, at
the moment QGIS cannot be built with an independent plugin for GRASS (that
means saving HDD space), but that's another story....
>> I would have no hesitation in including FWTools, native GRASS and QGIS
>> packages for MS-Windows by Marco
again, please note that the libraries included into the FWTools cannot be
used by the binaries of both GRASS and QGIS...
Regards,
Marco
-----------------------------------------
Reply to: