Note that there are some explanatory texts on larger screens.

plurals
  1. POsetting up mercurial/kiln subrepos on osx
    text
    copied!<p>I have been trying to follow the instructions in the answer to <a href="https://stackoverflow.com/a/4459853/830899">this question</a>, using kiln.</p> <p>i'd like to be able to arrange things as follows:</p> <ul> <li><code>/somepath/thirdparty</code> maps to a kiln repository "thirdparty" and contains assorted code</li> <li><code>/somepath/common</code> maps to a kiln repository "common" and contains shared code i have written</li> </ul> <p>and</p> <ul> <li><code>/somepath/project1</code> maps to kiln repository "project1" </li> <li><code>/somepath/project1/thirdparty</code> maps to branch of thirdparty above </li> <li><code>/somepath/project1/common</code> maps to branch of common above </li> </ul> <p>and</p> <ul> <li><code>/somepath/project2</code> maps to kiln repository "project1" </li> <li><code>/somepath/project2/thirdparty</code> maps to another branch of thirdparty above</li> <li><code>/somepath/project2/common</code> maps to another branch of common above </li> </ul> <p>I found that when I created the <code>.hgsub</code> file as instructed and 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).</p> <p>Anybody tried anything like this before, using Kiln?</p> <p>As I intend to develop a number of apps using the common code (and 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.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload