Question

我一直在努力遵循

/somepath/thirdparty maps to a kiln repository "thirdparty" 以及 contains assorted code
/somepath/common maps to a kiln repository "common" 以及 contains shared code i have written

以及

/somepath/project1 maps to kiln repository "project1"
/somepath/project1/thirdparty maps to branch of thirdparty above
/somepath/project1/common maps to branch of common above

以及

/somepath/project2 maps to kiln repository "project1"
/somepath/project2/thirdparty maps to another branch of thirdparty above
/somepath/project2/common maps to another branch of common above

I found that when I created the .hgsub file as instructed 以及 added/pushed it to Kiln, I could no longer view the Kiln files in the Kiln web file viewer — it displayed an obscure message about the Kiln "overheating" :-) Additionally, whilst it did automatically create the subfolders in the correct place, they were not populated with files, (possibly because the pull failed).

任何人在使用Kiln之前试图这样做。

As I intend to develop a number of apps using the common code (以及 potentially eventually release the library as open source), I would like to have it managed in discrete repositories. As some of the projects are for end clients however, I need to be able to give them a single repository that includes things as described above.

Answer 1

Kiln do ,目前不支持使用服务器上的“URLs”这一代用品。也就是说,你不能同时工作:

http://server/kiln/somepath/project1
http://server/kiln/somepath/project1/thirdparty

因此,你应该建立起来。页: 1

http://server/kiln/somepath/project1
http://server/kiln/somepath/project2
http://server/kiln/somepath/thirdparty
http://server/kiln/somepath/common

这简便——只是四个正常的存放处。然后是“项目”,创建<代码>hgsub。档案:

thirdparty = http://server/kiln/somepath/thirdparty
common = http://server/kiln/somepath/common

当你将这一资料推回Kiln时,它将通知并显示各子库的联系。然而,子库wont <>/strong>最终在服务器上封顶。因此,服务器上的任何<代码>项目1/第三方。

很显然,你想要这样做。如果你们有几个项目能够合作和使用一些共同的法典基础,那么你就希望“项目1”和“项目2”能够相互改变这一共同的法典基础。因此,在推动和从<条码>上拉动的这两个项目中,<条码>直线背书非常有用。
In Mercurial, we normally recommend that you use paths of the form common = common in the .hgsub file. This means that the server must support nested repositories. When Kiln doesn t support nested repos, you can use full paths instead.

当你最初设立这些子库时,你会记得,你需要人工更新。因此,与上述URLs一样,你将开办“项目1”:

$ hg clone http://server/kiln/somepath/project1 $ echo "common = http://server/kiln/somepath/common" > .hgsub $ echo "thirdparty = http://server/kiln/somepath/thirdparty" > .hgsub $ hg commit -m "Created subrepos"

这造成了最初的空置储存库。他们是空洞的,因为你 t告诉Mercurial,他们需要改变。 http://code>.hgsubstate。页: 1

0000000000000000000000000000000000000000 common 0000000000000000000000000000000000000000 thirdparty

居民点

$ cd common $ hg pull --update $ cd ../thirdparty $ hg pull --update $ cd .. $ hg commit -m "Updated subrepos"

该表更新了<代码>000... Line in .hgsubstate,同时更新了目前对这两个分题的提纲变更。 “项目1”的未来布局将通知<代码>hgsubstate文档,并确保更新此处提及的修订案文。

友情链接