[tor-bugs] #12406 [Tor bundles/installation]: use MinGW-w64 v3.1.0 for TBB 4.x
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Jun 17 15:26:38 UTC 2014
#12406: use MinGW-w64 v3.1.0 for TBB 4.x
------------------------------------------+------------------------------
Reporter: mcs | Owner: erinn
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor bundles/installation | Version:
Resolution: | Keywords: MikePerry201406R
Actual Points: | Parent ID:
Points: |
------------------------------------------+------------------------------
Comment (by gk):
Replying to [comment:3 mcs]:
> Replying to [comment:2 gk]:
> > Why is the change in fetch-inputs.sh necessary? I mean what does speak
against just bumping `MINGW_VER` to 6638 (which v3.1.0 is pointing to
IIRC)? I don't see the benefit of having the additional complexity as tags
in subversion can't be signed anyway (AFAICT).
>
> My SVN knowledge is very limited. It just seemed better to use a
symbolic tag, but we can stick with SVN revisions if you prefer. But –
and maybe I am misunderstanding svn revisions – isn't v3.1.0 revision
6434?
Maybe? :) I get checked out rev 6638 if I am running your branch. |svn
update| in the mingw-w64 dir tells me I am already at rev 6638. But you
might be right though. I guess rev 6638 is just the tag pointing to rev
6434...
> Actually, digging a little deeper it looks like the MinGW-w64 project
recently switched to git. The git hash for v3.1.0 seems to be
9418eaa1854320b57f40e29ec5bbc4f5717ecd58. Should we pull via git?
Sounds good. We could then get rid of the mingw-w64 SVN checkout related
code, I guess. Not sure if they sign their tags. If not, just pin the
commit we use (who knows where the tag is pointing to...).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12406#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list