El Martes, 14 de Junio de 2005 00:09, [EMAIL PROTECTED] escribió: > <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; > - href="../../cross-tools/x86_64/gcc-static.xml" > + href="../../cross-tools/mips/gcc-static.xml" > xpointer="xpointer(//[EMAIL PROTECTED]'installation']/screen[3])"/>
Looking at this, we could follow, for the installation and configuration sections, one of the two different ways that are showed above. Both have their pros a cons, and no one is used by default for now (both are mixed at this momment in the sources). The first one is to point the Xinclude in all archs to common commands and explanations founded on the firs file that contain them, following this directories priority pattne for archsr: common/, multilib/, x86/, mips/, mips64/, sparc/, sparc64/. In the above fragment for example, to point temp-system/x86_64/gcc.xml to cross-tools/mips/gcc-static.xml. That have the advantage that all the Xinclude will point to the file that contain the actual text, regardhless to what arch pertain both files. But have the cons that if an arch-specific change is needed on that included fragment, both the text and all the Xincludes that point to it in others archs files must be changed. The second is to keep the Xinclude the most arch auto-contained possible. In the same example, to point temp-system/x86_64/gcc.xml to cross-tools/x86_64/gcc-static.xml, having cross-tools/x86_64/gcc-static.xml as the unique file on that arch that point to cross-tools/mips/gcc-static.xml. That have the cons of create anidated Xinclude. If you go to the included file you will see another Xinclude instead the actual text. But has the advantage that if an arch-specific change is needed, only one file from other archs must be fixed. Of course, all the above is applicable only to few packages that are builded several times, most notabilly Glibc, GCC and the kernel. What of both ways should we to use? -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.com TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
