4 This document describes external dependencies and how I think I
5 should be tracking them. It is a bit outdated as of
6 <2012-10-04 Thu> but hopefully that will be fixed soon.
8 * Getting required external files.
13 darcs get http://common-lisp.net/project/lift/darcs
14 cd lift.darcs ; darcs pull
15 darcs get http://common-linsp.net/project/cffi/darcs/cffi
16 cd cffi.darcs ; darcs pull
19 We can use darcs-to-git script to convert (findable on github), and
20 ideally upload to GitHub, CommonLisp.net, or repo Git
21 public-repository repositories.
23 IS THIS A GOOD IDEA? Once it is there, we can register as a
24 submodule, and then use git submodule commands to get the versions
27 I think it's a good idea, only for core development. For
28 developers of CLS programs (away from core), provide the core
29 packages and have people develop on top of them.
31 ** Commands for external GIT:
34 cd $(LISPSTAT-GIT-TOPLEVEL-DIR) # from here, cd .. (hopefully!)
35 git submodule add git://cyrusharmon.org/pub/git/ch-asdf.git \
37 git submodule add git://cyrusharmon.org/pub/git/ch-util.git \
42 ## How do we update locally?
43 ## git submodule update ...?? (test using the submodule that we need to get when connected).