[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #30770 [Internal Services/Tor Sysadmin Team]: consider alternatives to the puppet mono-repo



#30770: consider alternatives to the puppet mono-repo
-----------------------------------------------------+--------------------
     Reporter:  anarcat                              |      Owner:  tpa
         Type:  defect                               |     Status:  new
     Priority:  Medium                               |  Milestone:
    Component:  Internal Services/Tor Sysadmin Team  |    Version:
     Severity:  Normal                               |   Keywords:
Actual Points:                                       |  Parent ID:  #29387
       Points:                                       |   Reviewer:
      Sponsor:                                       |
-----------------------------------------------------+--------------------
 another aspect of "how to publish our puppet repos" and how to collaborate
 is how to manage sub-repositories. expanding on the "mono-repo" problem
 discussed in #29387, i have found the following options:

  1. current "monorepo" approach
  2. pure librarian / r10k
  3. submodules
  4. git subtree: ​https://github.com/apenwarr/git-subtree
  5. git subtree (same?):
 ​https://github.com/git/git/blob/master/contrib/subtree/git-subtree.txt
  6. git subrepo ​https://github.com/ingydotnet/git-subrepo
  7. "myrepos": ​https://myrepos.branchable.com/

 i'll add more as i find them here. i should probably make a more detailed
 review of the advantages/inconvenients of all of those...

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30770>
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