[GRASS-user] 7.0.0 Mac OS X Install Notes

[Jeshua Lacock]

> On Feb 22, 2015, at 8:50 PM, Michael Barton <Michael.Barton at asu.edu> wrote:
> 
> I don't know why Jeshua wrote to you since I maintain the wikidot site.

Hi Michael,

To be clear, I didn’t write to William, I wrote to the list to which he replied.

> As for the other issues, I'll respond
> 
> 1. There IS a link to the Kyngchaos frameworks page in the menu on the right side that shows up on every page. On that frameworks page, it is clearly stated that PROJ and UnixImageIO are a part of the GDAL Complete package
> 
> 2. AFAIK, the order of installing the main frameworks packages makes no difference. The ones for which order matters are included in GDAL Complete. If I am wrong here, please let me know and I will put a note on the site.

On the main download page it does not state anything about installation order. I did not install GDAL first. Then I got several other errors. If it happened to me, I can only assume it will happen to others.

I am just throwing out a couple super simple steps that might make ones experience more pleasant - or with the permissions issue keep them from being able to use it at all.

> 3. No one has ever reported this permissions issue so far. I don't know what is causing it in this case (unless it is new for 7.0 stable).  AFAIK, the only permissions issue is the need to have a writeable director called "bin" inside the GRASS folder if you are installing extensions. This is a weird quirk of the extensions build system on the Mac. If there is a new permissions issue for 7.0 stable, it needs to be reported. But I have built it in exactly the same way as I've built all other builds recently.

It has actually happened with the betas for me I just neglected to report it. As it is, the package leaves a folder that the user will not have permission to access. This should not be a difficult thing to reproduce or fix. I would suspect that the folder is owned by root because root permissions are required to install, and you likely just need to clean up the permissions as I suggested.

Good news is your package can be fixed without even rebuilding the package - just take a look at the postflight script.


Best,

Jeshua Lacock
Founder/Engineer
3DTOPO Incorporated
<http://3DTOPO.com>
Phone: 208.462.4171