Hi, Am Freitag, den 22.11.2013, 23:36 +0100 schrieb Johan Tibell:
What's the difference between the ghc and ghc-complete repos?
ghc-complete is a repository that contains (besides some scripts) only one file, a fingerprint: ~/build/haskell/ghc-complete $ cat fingerprint .|5874f13fd83409b28c4f781a93e80f4605d0593e libffi-tarballs|a0088d1da0e171849ddb47a46c869856037a01d1 libraries/Cabal|e3e3702a6997f9a431ca562156cf667c93bd0e5e libraries/Win32|3da00d80f2fd7d1032e3530e1af1b39fba79aac3 libraries/array|26ff04744117b0ad8233a1a2b5635fa1277b88d9 libraries/base|f3e5ad387c2e77bed36fc41b6319514fc38e59f2 libraries/binary|2799c25d85b4627200f2e4dcb30d2128488780c3 ... It is updated regularly (currently a cronjob every 15 minutes, ideally by push hooks), and each push triggers a build of exactly these recorded versions of all components via travis: https://travis-ci.org/nomeata/ghc-complete/builds This way, travis builds are triggered also by updates to, say, the testsuite, it allows for reproducible builds, and possibly allows bisecting and other stuff. It is a weak substitute for having everything in proper submodules. As a developer, you usually would not interact with ghc-complete. Greetings, Joachim -- Joachim “nomeata” Breitner mail@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata@joachim-breitner.de • GPG-Key: 0x4743206C Debian Developer: nomeata@debian.org