Hi there, I'd be interested in some feedback, should anyone have a chance to look at things, as to how best to leverage SVN to add "mutiple rendering pathways", so let me expand on that.
The build system for the vanilla LFS book already has the ability to branch on SysV or SysD. Thomas's patch adds multilib capability to either of those pathways. I am looking to apply a "PkgUser" (the More Control hint) approach on top of that. My local (file-backed) SVN repo contains a mix of direct PkgUser modifications, along with things such as 2>&1 | tee ../make.out being added into (hopefully) all of the various make commands, so including the "make check/test" and "make install" stuff. I also make a few changes to <scree><userinput> blocks so as to remove some things from the output generated by the book's Makefile's dump-commands target. What's not been clear to me in trying to store changes within my local SVN repo is how to seperate things out so that for example, i could apply a "PkgUser" SVN diff to a vanilla LFS XML source tree if it hadn't had Thomas's Multilib patch already applied. Another one along the same lines is the make redirection stuff that I add into my own books. Whilst that's not realy PkgUser specific, i could see that a standlone SVN diff that applied just that might be useful to some folk, but again it's not clear how to seperate things out when using SVN across the two "regimes" I am adding stuff on top off, namely, the vanilla LFS and the Multilib additional source. Any pointers/insight welcome. Kevin PS I have a rendering of my current book but am yet to stick it up on the internet in case anyone wnats to take a look.: RSN. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
