[Qgis-developer] OSX packages

[Andreas Neumann]

Hi William,

The OSGeo4W installer allows to have a local package repository in your 
LAN (e.g. on a network drive). But I agree, it would be a lot of work to 
have something similar on OSX - and then it would be too complicated for 
the OSX people (except the Unix tribe among the OSX users).

I regard Oracle support as non-standard usage where it is ok to install 
separate frameworks/libraries. But it would be very nice if the standard 
package could install without the extra framework requirements. I know, 
you would never be able to satisfy all users, but probably 90%. I don't 
know how many of the QGIS OSX users really need the non GPL stuff (like 
ecw, MrSID). I always tell users to stay away from these proprietary 
formats ...

Andreas

On 07.11.2014 01:46, William Kyngesburye wrote:
> My ignorant understanding of the (windows, right?) osgeo installer is that it downloads the bits you choose to install.  That's a bit complex for me to setup and maintain, and I would prefer to stick to standard OS X installer mechanisms.  I personally don't like installer installers (and stores for that matter), it makes for unecessary redownloading when installing on multiple computers, or reinstalling.
>
> On Nov 6, 2014, at 10:48 AM, chris marx <chrismarx at gmail.com> wrote:
>
>> I'd just like to second the notion of an easier install for mac, an installer would be great, and I'd really like it if, just like the osgeo installer, you could specify that you want the oracle support installed too-
>>
>> On Thu, Nov 6, 2014 at 11:41 AM, William Kyngesburye <woklist at kyngchaos.com> wrote:
>> It should be possible, there is a build option to do that, though I haven't fully tested it.  (GSL is bundled, I keep forgetting to ask someone to fix the QGIS donwload page to remove that requirement.)
>>
>> You would miss out on GDAL driver plugins, especially those with non-GPL-compatible licenses.  They would still need separate installers, and I would have to figure out where to install them.  Probably a QGIS application support mirroring GDAL's, though it could share use of the normal GDAL plugins.  Not in the application, not proper.
>>
>> Required python modules are another thing that would be needed to be bundled.  But users would still need to separately install other Python modules needed by any QGIS plugins they installed.
>>
>> About the installer vs. drag-n-drop: the installer is needed for compiling the python scripts and creating the browser alias.  Drag-n-drop is not the only "normal" installation method on OS X.  Installers are just as "normal".
>>
>> Besides sharing GDAL with other software, GDAL and the Python modules are very useful on their own, and I hear from many people who do use them separately from and alongside QGIS.
>>
>> One thing I'm not sure about, if QGIS knows to specify the GDAL resource dir (datums, projections, ...) if it's not at the default location programmed into GDAL.  And that goes for not only GDAL as a library, but the GDAL tools and GDAL python.  (and other libraries that have resource dirs like PROJ and geotiff)
>>
>> I have considered an alternative: putting the current GDAL and Python module installers on the QGIS installer disk image.  It's one download, but users would still have to install each of them in the right order.
>>
>> The problem with this, and another problem with the bundling method, is that when any of the pieces change, I have to package the whole thing again (and with bundling that means saving the compiled source and running the make install again to do the bundling, and hope that something doesn't trigger a recompile).  And the user has to download the whole monster again and install it.
>>
>> On Nov 6, 2014, at 3:20 AM, Andreas Neumann <a.neumann at carto.net> wrote:
>>
>>> Hi,
>>>
>>> I wonder if we could offer "all in one" OSX QGIS packages in the future?
>>>
>>> The average OSX user is afraid of installing separate frameworks - even if its very simple. The normal install way on OSX is just drag and drop to the applications folder.
>>>
>>> Is there a particular technical reason why we cannot include GDAL/GSL into the QGIS package? I know that it wouldn't be shared with other FOSSGIS software then - but would this matter a lot?
>>>
>>> Andreas
>>>
>>>
>>> _______________________________________________
>>> Qgis-developer mailing list
>>> Qgis-developer at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> -----
>> William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
>> http://www.kyngchaos.com/
>>
>> [Trillian]  What are you supposed to do WITH a maniacally depressed robot?
>>
>> [Marvin]  You think you have problems?  What are you supposed to do if you ARE a maniacally depressed robot?  No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer...
>>
>> - HitchHiker's Guide to the Galaxy
>>
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> -----
> William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
> http://www.kyngchaos.com/
>
> [Trillian]  What are you supposed to do WITH a maniacally depressed robot?
>
> [Marvin]  You think you have problems?  What are you supposed to do if you ARE a maniacally depressed robot?  No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer...
>
> - HitchHiker's Guide to the Galaxy
>
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer