grass: upgrade to 7.0.0

[mojca (Mojca Miklavec)]

Grass developers released version 7.0.0beta2.

I prepared a version for testing.

Currently open tickets:

• #32797 grass does not ensure it's UsingTheRightCompiler
• #40307 grass @6.4.2: Unsupported compiler detected
• #42161 grass: compatibility with wxWidgets 3.0
• #42203 grass: allow building without GUI

I would suggest to start working on these issues on top of version 7.0 as opposed to trying to fix 6.4. There doesn't seem to be much response from developers about fixing problems in version 6.4, one particular problem is compatibility with wxWidgets 3.0.

[cooljeanius (Eric Gallager)]

Oh good, you already have me on CC... I will try to test your new "version for testing" once I finish shaving these yaks...

[petrrr]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Looks like ​7.0.0beta3 was released.

[mojca (Mojca Miklavec)]

I committed the necessary change to my user tree (linked above). We probably need more variants for mysql and maybe less for postgresql. I'm not sure to what extent Grass 7.0.0beta3 works better with wxWidgets 3.0, but I would prefer to drop support for 2.8 if possible as that only confuses matters and wxWidgets is at least supposed to be supported upstream.

[fhgwright (Fred Wright)]

Given that Grass 7.0 is still considered beta, and that it involves some file format changes (admittedly with conversions available) as well as many user-visible changes, it's probably premature to consider this an "update" to the existing 6.4-based port. Thus, I'd suggest something like "grass-beta" for now.

Meanwhile, it wouldn't hurt to update the existing port to 6.4.4 on general principles, though that may not help the GUI issues.

It also might be worth considering bumping the default Python variant to 2.7.

[petrrr]

I guess we use the -devel postfix in such occasions and we should adhere to this convention here as well. When we want to use grass 7 as default version, we move it to grass and grass-devel becomes replaces_by grass.

[mojca (Mojca Miklavec)]

Default python is not 2.7 for a reason: py27-wxpython-2.8 conflicts with py27-wxpython-3.0. Once we switch to py27-wxpython-3.0, life will get easier.

[petrrr]

I am just wondering why we do not commit this as either as grass-devel or grass7 ?

[petrrr]

BTW, I'd personally prefer grass-devel for the beta, because this avoids this ugly epoch bumps.

[petrrr]

I am just looking though the Portfile. Is there a good reason to stick with proj47? Can't we use proj, i.e. version 4.8? I have not found any hint that the current version would not be compatible.

[petrrr]

The mysql5 variant needs to be changed to comply with multiple mysql variants, see for example #43431.

[Veence (Vincent)]

Could it be possible to add a ‘console’ or 'no-gui’ variant, in order to build only the algorithms? This could be useful for people such as me, who only use Grass through the QGis plugin. Thanks!

[mojca (Mojca Miklavec)]

In the testing port (in my user space) I changed proj47 to proj. It's not clear to me what needs to be done about mysql (= which one should be default etc.).

The reason why the port hasn't been committed yet is because:

• there is no single confirmation claiming that the port works
• I was thinking of replacing the old grass, but then again it's not clear to me whether we should have grass7 or grass-devel or whether we should wait for the program to get out of the beta phase ... We could use grass-devel for now and then decide what to do with it when the official release gets out.

But I'm not the maintainer, so feel free to do whatever you want.

I would need to better understand how console/gui/python/wxwidgets work with each other and how to disable specific parts only. I believe that nogui is not desirable, so we would have to use +gui. But then: should +gui automatically select imply wxwidgets (and we could get rid of wxwidgets as a variant altogether)? What about python?

[petrrr]

Regarding the modifications to mysql5 variant, I guess comment:4:ticket:43431 gives good indications. I believe there is quite some consensus that mariadb55 should be the default, but maybe we should consult the dev list.

[mojca (Mojca Miklavec)]

We should try to get the version 7.0 working.

My proposal is still in my userspace, but I didn't yet finish patching DESTDIR. The file macosx/Makefile still needs a major review to make the destroot phase succeed.

[petrrr]

Grass 7.0 is ​stable now, so need for a -devel / -beta port.

Moreover: The requirements are not very explicit about versions, but I do not see any reason why grass would need to stick to proj47, grass is one of the few remaining ports which still depend on proj47.

I also would like to request to add a +postgresql93 variant. Would you like me to file a separate ticket on this?

@mojca: No chance that you become a maintainer ;-)

[mojca (Mojca Miklavec)]

Both proj and postgresql93 have been addressed in the above given link.

I don't want to become a maintainer of software for which I don't have the slightest clue how to use it.

[Veence (Vincent)]

I have a Portfile for Grass 7.0.2 that compiles and installs correctly. However, it does not work. Does anybody want to help me on this?

[mojca (Mojca Miklavec)]

I'm assigning this ticket to Vincent who already created a port grass7 in r142757 and kept updating it.

Perhaps this ticket could be closed already? Perhaps we should rename grass to grass6 (or perhaps better: remove grass6)?

At some point I would like to get rid of py-wxpython-2.8 (see ticket #46351) and grass 6 is one of two ports that still keep using it.

[Veence (Vincent)]

Is there anything I can do for this. The Grass package is up-to-date right now (7.2)

I'm closing this ticket, if you need anything else, please reopen it.