blocks|key|270526|text|在你的git服务器上|type|unstyled|depth|inlineStyleRanges|entityRanges|data|270527|镜像同步存储库初始化镜像--|270528|+-u+#--+https://android.googlesource.com/platform/manifest+is+the+key|unordered-list-item|offset|length|270529|
|270530|repo+|270531|270532|270533|270534|因为您指定了--+mirror，所以创建的所有repos都将是“空的”repos，这是git正确的创建镜像的方式，除非您是git超级主子。|270535|在您的客户端上：|270536|270537|repo+init+-u+git+@git.yourserver.com：/manifest.git#你可以使用不同的方式访问你的git服务器；我必须为这个例子做一些假设。|ordered-list-item|270538|还没有repo同步。你的货单可能是错的。看一下符号链接的.repo/manifest.xml...点击并阅读顶部的<remote+fetch=""...它可能指向android.googlesource.com。但如果上面写着“..”我想这意味着“回到我的服务器”，所以你可以跳到步骤6)。但如果它确实指向另一台服务器(不是您的服务器)，则转到步骤3.|style|CODE|270539|cd+.repo/manifests|270540|vim+.repo/manifests/default.xml+(或您的active+manifest.xml是什么)。修复default.xml的<remote+fetch="CHANGE+ME"，指向你的git+server|270541|attempt+a+repo+sync。它应该只从你的存储库中拉出。如果没有，请停止存储库同步，然后再次尝试修复default.xml。|270542|一旦您看到存储库同步在您的测试计算机上工作，然后提交default.xml+back+in+(git+commit;+git+push)，这样团队中的其他成员在从您的服务器执行repo+init;+repo+sync时将具有‘no-default.xml-edit’体验。|270543|270544|270545|一旦你看到一个‘无清单编辑’的repo+init;+repo+sync工作，然后再次转到你的default.xml，只需开始添加新的XML元素以及大量其他已有的Android项目元素；这些新元素将指向你的自定义项目。对于这些新项目，只需像往常一样对它们进行git初始化，并确保它们有一个与相同<default+revision="whatever_branch_you_see_here"匹配的分支，这样repo+sync在遇到这些新项目时就会成功。|270546|如果您确实在清单<default+revision=""元素中设置了默认分支，那么只需让everyone设置一个本地分支，以遵循修订属性中指定的远程分支。因此，例如，如果<default+revision="branch_a"在您的清单中，在您执行repo同步之后，当您cd到感兴趣的子项目时，请执行以下操作：|270547|git+checkout+-b+branch_a+origin/branch_a|270548|然后，如果用户的分支(据我所知，没有repo命令可以推送)，如果其他人在推送之后执行./repo+sync，他们将从原始用户那里获得这些更改...只要您使用相同的清单并实际推送到该清单指定的默认修订(分支)。|270549|这是最简单的方法。如果你想创建真正的功能分支，那么如果你想让'repo+sync‘正常工作，你就必须更有规律地编辑你的清单……当你这样做时，你必须与团队的其他成员沟通，以获取你的清单版本。或者，如果只有一个或两个git+repos你正在接触，那么你可以放弃repo+sync和git+push/pull，就像那些repos上的正常情况一样，忽略你大量迭代的安静树的其余部分。最终，对我来说，这听起来像是一条更简单的道路。我会尽可能忽略repo；只将其用于“所有项目”同步，并在专注于1到2个项目时将其留在一边。|270550|关于从上游获取更新。我认为这样做的方法是改变你的default.xml指向你的原始git位置(如android.googlesource.com)，做一个回购同步，以使所有新的东西合并在一起，一旦完成同步，提交回你的回购。我还没有做到这一点；所以我不能太具体，但这是我计划如何做到的。|270551|我忽略了上面的服务器管理细节。例如，您需要调用git服务器上某个目录中的repo+init，以使其成为可用的git存储库；我假设您知道如何管理git服务器。|270552|entityMap|0|LINK|mutability|MUTABLE|url|https://android.googlesource.com/platform/manifest^0|0|0|8|1E|0|0|0|0|0|0|0|0|0|0|1|1L|G|1|1|22|P|1|1|1B|K|2G|K|1|0|0|F|K|42|1C|5M|9|0|8|K|2D|S|0|0|14|0|16|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1Z|8|@]|9|@$G|20|H|21|1|22]]|A|$]]|$1|I|3|J|5|6|7|23|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|24|8|@]|9|@]|A|$]]|$1|M|3|J|5|6|7|25|8|@]|9|@]|A|$]]|$1|N|3|-4|5|F|7|26|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|28|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|29|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|2B|8|@]|9|@]|A|$]]|$1|X|3|Y|5|W|7|2C|8|@$G|2D|H|2E|Z|10]]|9|@]|A|$]]|$1|11|3|12|5|W|7|2F|8|@]|9|@]|A|$]]|$1|13|3|14|5|W|7|2G|8|@$G|2H|H|2I|Z|10]]|9|@]|A|$]]|$1|15|3|16|5|W|7|2J|8|@]|9|@]|A|$]]|$1|17|3|18|5|W|7|2K|8|@$G|2L|H|2M|Z|10]|$G|2N|H|2O|Z|10]]|9|@]|A|$]]|$1|19|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|2R|8|@$G|2S|H|2T|Z|10]|$G|2U|H|2V|Z|10]|$G|2W|H|2X|Z|10]]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|2Y|8|@$G|2Z|H|30|Z|10]|$G|31|H|32|Z|10]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|33|8|@$G|34|H|35|Z|10]]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|36|8|@$G|37|H|38|Z|10]]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|39|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|3A|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|6|7|3B|8|@]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|3C|8|@]|9|@]|A|$]]]|1Q|$1R|$5|1S|1T|1U|A|$1V|1W]]]]

On your git server

<ol>
<li>repo init -u <a href="https://android.googlesource.com/platform/manifest" rel="noreferrer">https://android.googlesource.com/platform/manifest</a> --mirror # --mirror is the key</li>
<li>repo sync</li>
</ol>

Because you specified --mirror, all repos created will be 'bare' repos, which is the git-correct way to create a mirror unless you are a git uberlord.

On your client:

<ol>
<li>repo init -u git@git.yourserver.com:platform/manifest.git # you may use a different means of accessing your git server; I have to assume something for this example.</li>
<li>no repo sync yet. Your manifest is probably wrong. Look at the symbolic linked .repo/manifest.xml... cat it and read at the top the <code>&lt;remote fetch=""</code>... it probably points back to android.googlesource.com. but if it says '..' I think that means 'come back to my server', so you can skip to step 6). But if it does point back to another server (not yours), then go to step 3.</li>
<li>cd .repo/manifests</li>
<li>vim .repo/manifests/default.xml (or whatever your active manifest.xml is). </li>
<li>Fix default.xml's <code>&lt;remote fetch="CHANGE ME"</code> to point back to your git server</li>
<li>attempt a repo sync. It should pull only from your repository. If it doesn't, stop the repo sync, and try to fix default.xml again. </li>
<li>Once you see repo sync work on your test machine, then commit default.xml back in (<code>git commit; git push</code>), so that others on the team will have 'no-manifest-edit' experience when they <code>repo init; repo sync</code> from your server.</li>
</ol>

Once you see a 'no manifest edit' <code>repo init; repo sync</code> work, then go to your default.xml again, and just start adding new XML elements along with the tons of other existing Android project elements; these new elements will point to your custom projects. For these new projects, just git init them as you normally would, and make sure they have a branch matching the same <code>&lt;default revision="whatever_branch_you_see_here"</code> so that a <code>repo sync</code> will succeed when it encounters these new projects.

If you do indeed set a default branch in your manifest <code>&lt;default revision=""</code> element, then just have everyone make a local branch set to follow the remote branch specified in the revision attribute. So, for example, if <code>&lt;default revision="branch_a"</code> is in your manifest, after you do a repo sync, when you cd into a sub-project of interest, do a :

<code>git checkout -b branch_a origin/branch_a</code> 

Then, if the user <code>git push</code>'s (there is no repo command to push, as far as I'm aware), and if someone else does a <code>./repo sync</code> after that push, they will get those changes from the original user... as long as you are using the same manifest and actually pushing to the default revision (branch) specified by that manifest.

That's the simplest recipe. If you want to make actual feature branches, then you'll have to edit your manifest more regularly if you want 'repo sync' to just work... and you will have to communicate to the rest of the team to grab your version of the manifest when you do that. Alternatively, if it's just one or two git repos you are touching, then you could just forego repo sync and git push/pull like normal on those repos and ignore the rest of the quiet tree for the times you are heavily iterating. This sounds, ultimately to me, like a simpler path. I'd ignore repo as much as you possibly can; only using it for 'all project' syncs and leaving it alone for the times you are focusing on 1 or 2 projects. 

Regarding getting updates from upstream. I think the way to do that is to change your default.xml to point back to your original git location (like android.googlesource.com), do a repo sync to cause all the new stuff to merge in, and once done with the sync, commit back up to your repo. I haven't done this yet; so I can't be too specific, but this is how I plan to do it. 

I'm ignoring server administration details above. For instance, you need to call the repo init in a certain directory on your git server to cause it to be an available git repository; I'm assuming you know how to administer your git server.

I want to develop on top of Android using a local Android repository server. I need to add several new git repositories to the hierarchy of gits, and I need to modify existing android sources for a custom tailoring of Android.

What is the "correct" way to clone the entire Android source tree of git repositories, such that I can push/pull to/from a common local repository server, and still easily pull new changes from Android upstream?

I am specifically looking for advice on how to use the <code>repo</code> script for interaction with my own server, and how to set up the <code>manifest</code> git repository and managing branches therein.

Cloning Android sources to a local repository server

服务器

Android

我想在Android上使用本地Android存储库服务器进行开发。我需要添加几个新的git存储库到gits的层次结构中，并且我需要修改现有的Android源代码，以便定制android。克隆git存储库的整个Android源代码树的“正确”方法是什么，这样我就可以推送/拉入/拉出公共本地存储库服务器，并且仍然可以轻松地...

问将Android源代码克隆到本地存储库服务器
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Android源代码克隆到本地存储库服务器EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Android源代码克隆到本地存储库服务器
EN