| > Incidentally, just to confirm, I never have to even look in validate.mk do I? It's 100% validate's | responsibility. | | validate.mk is to validate what build.mk is to make, i.e. if you want | the default settings then you can ignore validate.mk, but if you want to | change something then that's the place to change it.
Great, tha's fine. Did you mean "validate-settings.mk is to validate as build.mk is to.."? (Maybe it should be called "validate.mk".) Worth documenting on the Wiki with the instructions about "run validate"? | > Excellent thank you. And is the "core lib" and "extra lib" terminology described anywhere on the | Wiki? | | It's on | http://hackage.haskell.org/trac/ghc/wiki/DarcsRepositories | at least (except we use "library" and "package" interchangeably). | | Although the terminology does clash with | http://hackage.haskell.org/trac/ghc/wiki/PackageReorg | so perhaps we should rename to "boot" and "extra" instead. Aha! That's why I'm confused. It would be helpful to use consistent terminology. And it'd be helpful to say here http://hackage.haskell.org/trac/ghc/wiki/DarcsRepositories what the "semantics" of "core" (or perhaps now "boot") is. Such as The "ghc-boot" packages are the ones needed to build GHC itself; that is, to build the stage2 compiler. If that's what it means! And are those ghc-boot packages precisely the ones that are needed to run the validation tests? If so, it'd be good to specify that too. Sorry if this seems picky; it's just that I am trying to understand and then to retain my understanding. Simon _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
