Created attachment 165894 [details]
update to 0.11.2
Thank you for this.
There is a reason why I have not updated this port is that, in my opinion, and putting a nice fine point on it, the actions of bitcoin-core over the last months have been actively malicious.
It is my opinion that this port should switch to some other repo. However, -unlimited seems poorly managed, -xt is too broad. My current choice is -classic, when they tag a stable release.
So, as to this - should I approve it? The more I think of it, the more I answer no, mostly because it includes the RBF stuff that should never have been committed.
I'm not sure its our job to make decisions based on subjective things like that.
While, and until the bitcoin ecosystem players get their stuff sorted out, we need to remain objective and aligned with the purpose of ports in general.
Since bitcore-core is synonymous with 'bitcoin' at the moment, the existing name for this port remains suitable, and it's more than likely users want it to remain up to date, independent to what the outcome of the current debate out there in the world is.
+1 on landing the update
(In reply to Kubilay Kocak from comment #4)
Ok, yeah. Much as I don't like it, keeping the port up-to-date with -core probably should be done, until a better option comes about.
With reservations, approved. My testing shows this update builds and runs well.
A commit references this bug:
Date: Sat Jan 23 17:35:17 UTC 2016
New revision: 407045
Update to upstream release 0.11.2
Submitted by: firstname.lastname@example.org
Approved by: email@example.com (maintainer / alternative e-mail address)