This thread is similar to the old thread by Gerard ("What if the book
wasn't a book anymore") by title, but not by intentions. The old
thread was just an invitation to brainstorming related to presentation
of ideas from the reader's viewpoint. This thread is meant to be more
technical and conservative. You may assume, for the purposes of this
thread, that LFS will still be a website that provides some
educational material for reading online, and maybe some
non-interactive buildscripts that the reader may modify and run.When Jeremy and I worked on the LeafOS project, a problem naturally appeared: if we are going to support more than one package manager, or an optional package manager, there is the need to keep instructions for multiple variants in sync. I.e., the result of building a package manually and building/installing an RPM should be the same, except for explicitly documented differences. Syncing the instructions manually is not really a viable option, so we need something else. Unfortunately, the current DocBook toolchain is meant to produce a single book with instructions that are meant for copying and pasting. It is not suitable for generating both the non-PM-aware instructions and spec files from the same source, and is not able to modify the surrounding text accordingly. Worse, we don't even have a mockup HTML of how this should look like! So, please express your ideas in the following areas: 1) How should the readline page in a PM-aware-book look like? A spec file can be taken from http://gitweb.dwcab.com/?p=pound.git;a=blob;f=readline/readline.spec;h=5c24f5184a7432b2ade5dbbdf0b5f35a26eeaede;hb=HEAD (of course, it currently contains RPMisms such as %{_lib}, and things that RPM can find out by itself, such as "Requires(post): /usr/bin/install-info" - please ignore this for now). Readline is going to illustrate a typical package that: * provides a shared library (and thus, for the future soversion migration, has the development files to be split), * needs the same patches as in the non-PM-aware book, * needs a post-installation step, * has configuration files (/etc/inputrc). 2) How should the bash page in a RPM-based book look like? The difference is that an extra patch, bash-3.2-rpm-requires.patch, is needed in te RPM book. Template spec file, subject to the same criticism that has to be ignored for now: http://gitweb.dwcab.com/?p=pound.git;a=tree;f=bash;h=62805dac94304e519e665322e08ecc810c6eca14;hb=HEAD 3) How (from what form of sources) should all of this stuff be generated? -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
