Date: Thu, 17 Sep 2020 07:31:08 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 249360] net/shadowsocks-libev: update to 3.3.5 Message-ID: <bug-249360-7788-btavL8bigv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-249360-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-249360-7788@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=3D249360 --- Comment #3 from xiaoding+freebsd@xiaoding.org --- (In reply to daniel.engberg.lists from comment #2) We are always tracking upstream release in priority over a specific commit.= For example, this time we upgrade from v3.3.2 to v3.3.5. However, the upstream does not appear to publish release at a steady pace. = The release v3.3.2 to v3.3.4 all failed to build on FreeBSD-CURRENT, while the master branch succeeded to build. Before this patch there is no release tag available. v3.3.5 was created after a request. There are two reasons to keep current way: 1) The fetching method works well. 2) Checking out from GitHub repo is a more flexible way if we cannot expect= a release, we can check out from commit id instead. --=20 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-249360-7788-btavL8bigv>