Date: Wed, 24 Dec 2014 16:01:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196248] net/libsrtp: Upgrade to latest from GitHub Message-ID: <bug-196248-13-T8YZp4QTi3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196248-13@https.bugs.freebsd.org/bugzilla/> References: <bug-196248-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196248 --- Comment #5 from Mikhail T. <mi@ALDAN.algebra.com> --- (In reply to Kubilay Kocak from comment #4) > The changeset in question looks like it was made after v1.5.0 was tagged. It > was also made a few commits after 2_0_0_dev was branched from 1.5.x. Since nothing in our ports-tree seems to depend on net/libsrtp at the moment anyway, I'd rather our port offered the very latest from upstream. > a) Grab v1.5.0 tag, and backport the commit you want. (A raw diff in /files > should be enough) > b) Grab 2_0_0_dev at that commit, and set DISTVERSION accordingly The trouble with following such branches is that the version (DISTVERSION) does not change even after the upstream makes another commit. Thus, the timestamp (and the commit tag/hash/id) remains the only way to track the upstream sources in the sortable way. Yes, going from timestamp back to "normal" versions (like N.M.K) will be difficult, but there is not really a good alternative. Would it look better as 2.0.0.20141224 ? > As far as GH_* variables go, it's better learning how they are used. Jump on > #freebsd-ports or #bsdports any time to get help :) Thanks for the offer, but I was hoping, that you'd put an example right here. If you don't feel like it, then let's leave this PR between myself and the port's current maintainer. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196248-13-T8YZp4QTi3>