Re: tor-dev review and commit request
Christian Sturm <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.pkgsrc.wip.review |
|---|---|
| Message-ID | <[email protected]> |
Christian Sturm wrote: > Hi, > > please review (and fix ;-)) wip/tor-dev! > > The latest commit updated tor to the final version (it's not > tagged as alpha/beta/rc anymore) of the 0.2.1.x-branch or in > other words: This version is (or will be - it's not officially > announced yet) the new tor release. > > With tor-dev I usually track the unstable versions of tor, but > since this is a fairly big step from 0.2.0.35 (net/tor) I think > it should be tested a bit, before this replaces net/tor. > > If you have commit access please update net/tor with the contents > of wip/tor-dev, but please don't remove it. I will update > wip/tor-dev to the new unstable branch once the current version > is in net/tor. > > The only change from 0.2.1.17 is: > "Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent." > > So, if 0.2.1.17 was okay this one should also work. > > For a (big) list of changes from the last release see: > https://git.torproject.org/checkout/tor/master/ReleaseNotes Okay, I've been a bit to fast. 0.2.1.19 has been released, which means the 0.2.1.x branch is still unstable. Please don't move it to net/tor yet. I shouldn't have trusted the removal of the -rc tag. Anyway, the final release is coming nearer, so please review wip/tor-dev! Oh, pkglint gives warnings, but AFAIK they can be ignored from what I found in the mailing list archives. Is this (still) true? Greetings, Christian ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july