graphics/osgearth: Update to 2.7
ClosedPublic
Actions

Authored by woodsb02 on May 13 2016, 8:06 AM.

Details

Reviewers

Commits

rP415199: graphics/osgearth:

Summary

graphics/osgearth:

Update to 2.7 (this new version also allows osgearth to build against osg-3.4.0)
Rename and update patch of src/osgEarth/ThreadingUtils.cpp (pet portlint)
Add patch to removed unnecessary FirstPersonManipulator include from osgearth_skyview [1]

[1] https://github.com/gwaldron/osgearth/commit/bd36290687f6884c17c622ca57442e60c1ec50b8#diff-091cce4318b0ef98b4ce05f80e3d0762

PR: 209236
Approved by: lbartoletti@tuxfamily.org (maintainer), xxx (mentor)

Test Plan

poudriere testport graphics/osgearth

Repository

rP FreeBSD ports repository

Lint

No Lint Coverage

Unit

No Test Coverage

Build Status

Buildable 3715
Build 3758: arc lint + arc unit

woodsb02 retitled this revision from to graphics/osgearth: Update to 2.7.

woodsb02 updated this object.

woodsb02 edited the test plan for this revision. (Show Details)

woodsb02 added reviewers: adamw, mat, koobs.

graphics/osgearth/Makefile
13	This should be `minizip:archivers/minizip`.
graphics/osgearth/distinfo
1–2	Please update your ports tree and run make makesum again.

As per comments from mat:

woodsb02 marked 2 inline comments as done.May 13 2016, 9:12 AM

graphics/osgearth/Makefile
5	You should keep the DISTVERSIONPREFIX line, the `2.7` bit is a branch name, and not a tag, so it's going to move, and by doing so, breaking this port.

As per comments from mat:

Also:

woodsb02 marked an inline comment as done.May 13 2016, 4:26 PM

graphics/osgearth/Makefile
5	TIL. In fact, I have put it back in, but not sure I fully understand. I tried to read up about the GitHub download URL format, and whilst there was quite a lengthy discussion about old vs new APIs, there was not much mention of branches. So, can I please ask for an explanation of why we want the filename to be gwaldron-osgearth-osgearth-2.7_GH0.tar.gz, and what that means for branches vs tag names?

graphics/osgearth/Makefile
5	The branch name is "2.7". When upstream commits to that branch, the branch names stays the same but the tarball changes, making checksum fail after every commit. The tag name is "osgearth-2.7". As long as the tag isn't slipped (which is very bad behaviour), the tarball is fixed. GitHub's API is really flexible. If you give it a branch name, a tag name, or a commit hash, it'll send you a tarball of that thing. There's no way to tell it which one of those you wanted (which is okay, because those names can't overlap anyway). The tarballs names look strange but that was an intentional choice to ensure that distfiles could never conflict. Does that answer the question?

woodsb02 marked 2 inline comments as done.May 14 2016, 8:00 AM

woodsb02 added inline comments.

graphics/osgearth/Makefile
5	Ah yes, I follow now. Sorry, it took a little while to click, but I now see that the tags/releases on the osgearth GitHub page are not labelled "2.7" but instead "osgearth-2.7", and therefore without the DISTVERSIONPREFIX it was not actually downloading the release, but the latest commit of the 2.7 branch! Thanks. Its all done, and this should be ready to commit.