Re: [GRASS-dev] where to make compiling instructions available

2020-06-02 Thread Michael Barton 
I've put the instructions and supporting files onto the wiki page you made. 
Thanks for setting it up!

https://grasswiki.osgeo.org/wiki/Compiling_on_MacOSX_using_Anaconda

I think it all reads and links fine now, but it took a lot to get it formatted 
and linked correctly. Mediawiki is an infuriating variant of standard wiki and 
markdown.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: 'http://www.public.asu.edu/~cmbarton, https://complexity.asu.edu/csdc'



















On Jun 2, 2020, at 2:03 AM, Nicklas Larsson 
mailto:n_lars...@yahoo.com>> wrote:

Hi!

At this point I think the building instructions for anaconda (and later 
macports) should be placed in grasswiki as a new page linked from "Compile and 
Install" mac section [1]. Maybe: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__grasswiki.osgeo.org_wiki_Compiling-5Fon-5FMacOSX-5Fusing-5FAnaconda=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=oJi6OFZdzEJSCtUfsG9WNrH4x_wu5Fm1Yv5pZcltUNw=Im8NH4J8EQ-2ZwfWaxxFCosFb2N7wAwnDiQlq2wNyWM=
 .

I know we discussed [2] replacing/updating the text of macosx/ReadMe.md file, 
but I realised that that particular instruction (however outdated) is related 
to the whole of the content of that directory (which in turn is presently not 
functional, reported as issue #457 [3]). So I believe we should leave that 
directory and the ReadMe as is, until the issue is addressed.

The new wiki pages with instructions for anaconda and macports may perhaps be 
referenced to in INSTALL file.

Setting up a build script in source for GitHub Actions would be more than 
welcome(!), but doesn’t contradict the idea of publishing the instructions on 
wiki.


Nicklas


[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__grasswiki.osgeo.org_wiki_Compile-5Fand-5FInstall-23Mac-5FOSX=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=oJi6OFZdzEJSCtUfsG9WNrH4x_wu5Fm1Yv5pZcltUNw=BfhGgRy84E2upMUMcyyh7wE57sVczd8DYEYOAO0qKiE=
[2] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_OSGeo_grass_pull_636=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=oJi6OFZdzEJSCtUfsG9WNrH4x_wu5Fm1Yv5pZcltUNw=Sveq39CHdd8x5VsBRBmVd9N5dhS5sYzh6wzHijtrv0s=
[3] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_OSGeo_grass_issues_457=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=oJi6OFZdzEJSCtUfsG9WNrH4x_wu5Fm1Yv5pZcltUNw=8YPtGy_iqCKh7Rr7BnfAIelfYxk_-qT1IlQ_KKrhH8k=


___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] where to make compiling instructions available

2020-06-02 Thread Nicklas Larsson 
Hi!

At this point I think the building instructions for anaconda (and later 
macports) should be placed in grasswiki as a new page linked from "Compile and 
Install" mac section [1]. Maybe: 
https://grasswiki.osgeo.org/wiki/Compiling_on_MacOSX_using_Anaconda.

I know we discussed [2] replacing/updating the text of macosx/ReadMe.md file, 
but I realised that that particular instruction (however outdated) is related 
to the whole of the content of that directory (which in turn is presently not 
functional, reported as issue #457 [3]). So I believe we should leave that 
directory and the ReadMe as is, until the issue is addressed.

The new wiki pages with instructions for anaconda and macports may perhaps be 
referenced to in INSTALL file.

Setting up a build script in source for GitHub Actions would be more than 
welcome(!), but doesn’t contradict the idea of publishing the instructions on 
wiki.


Nicklas


[1] https://grasswiki.osgeo.org/wiki/Compile_and_Install#Mac_OSX
[2] https://github.com/OSGeo/grass/pull/636
[3] https://github.com/OSGeo/grass/issues/457 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Source code layout reorganization for G8

2020-06-02 Thread Maris Nartiss 
Hello list,
as G8 release is a great opportunity to break things, we could
reorganize our source code directory layout. At the moment we have
docker together with documentation and library intermingled with
MS-Windows for MacOSX. Bringing to a separate thread from "where to
make compiling instructions available"
https://www.mail-archive.com/grass-dev@lists.osgeo.org/msg59974.html

I have created an initial proposal page in Trac (linked to GRASS 8
planning page): https://trac.osgeo.org/grass/wiki/G8SourceLayout

Feel free to express your opinion — is it worth? How the new directory
layout should look like? Any technical restrictions?

Yes, it would break history, scripts, Make files = no fun. But if we
don't do it now, we'll be stuck till G9 release.

Waiting for feedback,
Māris.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev