#26877: Declare gcc version in rbm.conf ----------------------------------------+------------------------------ Reporter: sukhbir | Owner: tbb-team Type: enhancement | Status: needs_review Priority: Medium | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: tbb-rbm, TorBrowser201807R | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ----------------------------------------+------------------------------ Changes (by gk):
* keywords: tbb-rbm => tbb-rbm, TorBrowser201807R Comment: Hm, I am inclined to think it makes sense to keep those versions separated. Assuming we hit a toolchain bug for Linux which needs to get handled by using a newer compiler it does not seem smart to suddenly ship a new toolchain for Windows, too (or vice versa), especially if the stable series is affected. Thus, I think we should be conservative here and not have both linked together. On the other hand, the question is how often this actually happens and whether we could not work around that ad hoc without the need for bumping the compiler version of the unaffected platform. So, I don't feel too strongly here. Do we know why we had this separation in the past? I think we did not have that back in the `tor-browser-bundle` days. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26877#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs