Bug 192624 - /graphics/qgis installation fails with Grass Option
Summary: /graphics/qgis installation fails with Grass Option
Status: Closed DUPLICATE of bug 192605
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
: 192623 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-08-12 20:03 UTC by jjachuf
Modified: 2014-09-09 08:40 UTC (History)
2 users (show)

See Also:


Attachments
Update GRASS version (446 bytes, patch)
2014-09-02 19:06 UTC, Rainer Hurling
rhurlin: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description jjachuf 2014-08-12 20:03:44 UTC
It is solved by changing the line:

CMAKE_ARGS+=    -DWITH_GRASS:BOOL=TRUE -DGRASS_PREFIX=${LOCALBASE}/grass-6.4.3

for this:
CMAKE_ARGS+=    -DWITH_GRASS:BOOL=TRUE -DGRASS_PREFIX=${LOCALBASE}/grass-6.4.4

In the Makefile
Comment 1 John Marino freebsd_committer freebsd_triage 2014-08-12 20:17:19 UTC
*** Bug 192623 has been marked as a duplicate of this bug. ***
Comment 2 John Marino freebsd_committer freebsd_triage 2014-08-12 20:19:09 UTC
So everytime grass is updated this breaks because it's hardcoded?
Nobody can come up with a better method than hardcoding the version number?

Notify maintainer in CC
Comment 3 Rainer Hurling freebsd_committer freebsd_triage 2014-09-02 19:06:51 UTC
Created attachment 146693 [details]
Update GRASS version

Unfortunately, I am not aware of any straight forward method to avoid hard coding the GRASS version.

Sorry for the delay and thanks for the hint.
Comment 4 Rainer Hurling freebsd_committer freebsd_triage 2014-09-09 08:38:24 UTC
This patch is included now in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192605

So, it should be closed, after bug 192605 is committed, thanks.
Comment 5 John Marino freebsd_committer freebsd_triage 2014-09-09 08:40:12 UTC
We can close it now.

*** This bug has been marked as a duplicate of bug 192605 ***