From 863d79b36446bb2dbcc34d4f57c832ac2dc57f68 Mon Sep 17 00:00:00 2001 From: John Ericson Date: Mon, 6 Feb 2017 18:13:02 -0500 Subject: top-level: Introduce targetPackages and a "double link fold" Each bootstrapping stage ought to just depend on the previous stage, but poorly-written compilers break this elegence. This provides an easy-enough way to depend on the next stage: targetPackages. PLEASE DO NOT USE IT UNLESS YOU MUST! I'm hoping someday in a pleasant future I can revert this commit :) --- doc/cross-compilation.xml | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'doc/cross-compilation.xml') diff --git a/doc/cross-compilation.xml b/doc/cross-compilation.xml index 06a8919c2a19e..728616a9f2635 100644 --- a/doc/cross-compilation.xml +++ b/doc/cross-compilation.xml @@ -167,6 +167,11 @@ Because of this, a best-of-both-worlds solution is in the works with no splicing or explicit access of buildPackages needed. For now, feel free to use either method. + + There is also a "backlink" __targetPackages, yielding a package set whose buildPackages is the current package set. + This is a hack, though, to accommodate compilers with lousy build systems. + Please do not use this unless you are absolutely sure you are packaging such a compiler and there is no other way. + -- cgit 1.4.1