Re: [tor-bugs] #11641 [Tor bundles/installation]: change TBB directory structure to be more like Firefox's

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#11641: change TBB directory structure to be more like Firefox's
------------------------------------------+------------------------------
     Reporter:  mcs                       |      Owner:  mcs
         Type:  defect                    |     Status:  new
     Priority:  normal                    |  Milestone:
    Component:  Tor bundles/installation  |    Version:
   Resolution:                            |   Keywords:  MikePerry201405R
Actual Points:                            |  Parent ID:  #4234
       Points:                            |
------------------------------------------+------------------------------

Comment (by mcs):

 Replying to [comment:5 mikeperry]:
 > Nice work guys. Some comments:
 >
 > First, is there a reason why we can't have the 'Docs' subdir in the
 bundle at the top-level for all three platforms? I realize this is my
 oversight for not asking this sooner. If there is no problem with doing
 this, I can clean up the branch myself.

 The problem is that the updater will not be able to touch anything above
 the directory that contains Firefox.  So if by "top level" you mean "above
 the directory that contains Firefox" then that won't work.  We could
 create a shortcut on Windows and a symlink on Linux that point to the Docs
 directory.  On Mac OS, I am not sure how to really help people find the
 docs since they will need to know how to ctrl-click and choose "Show
 Package Contents" to see anything beyond the app package.  The best idea
 we have is to add a "Show Documentation Folder" feature inside Tor
 Launcher... if we can find a place for it in the GUI.

 > Second, in addition to the maint-3.6 tor-browser-bundle.git branch, it
 seems like we should create a new maint-0.2.5 branch for tor-launcher.git
 now, and start calling these new restructured tor launchers 0.2.6?
 Similarly, we probably want to make a separate tor-browser.git branch for
 the #9173 update, and probably the remoting stuff too. I can also do this,
 I am just stating it in case you have any alternate suggestions.

 That sounds like a good plan.

 > Third, for the tor-browser-bundle.git cleanups, I think we should be
 using the versions.nightly file for these changes, at least to start. Then
 we can think about building a 4.0-alpha (which will also have the updater
 in it, eventually) if the nightlies check out OK.

 OK, but we still need a branch within tor-browser-bundle.git since we did
 not conditionalize all of the path changes, files have been removed and
 moved, etc.

 > As far as merge timeline, I think we should shoot for merging this into
 'master' and doing all the branch restructuring after we are satisfied
 with #8402's behavior in the nightlies, and begin tagging that stuff for
 3.6.2 (hopefully mid next week).

 Sounds good to us.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11641#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs