On 10/12/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote these words on 10/12/06 00:15 CST:
> + <para>If you build <application>GNOME Doc Utils</application>
> + without <application>Python</application>, the
> + <application>pkg-config</application> support files will not be
> + installed. Ensure that they are installed with the following
> + command:</para>
> +
> +<screen><userinput>sed -i 's/@[EMAIL PROTECTED]/pkgconfig/'
Makefile.in</userinput></screen>
> +
> <para>Install <application>GNOME Doc Utils</application>
> by running the following commands:</para>
Something I've noticed that you do Dan, that has been discussed
before and determined that we should try do otherwise is individualize
commands with a description. LFS does this, but BLFS has always tried
to keep all the commands in the same block of commands to make cut
and paste just a bit easier.
So, instead of describing a command, then listing the command, as we
go forward could you just insert the new command into whatever
position is appropriate in the existing block of commands, and then
if necessary describe it in the 'Command Descriptions' section?
Sorry about that. I was actually actively thinking about this when I
wrote the command. Let me revise it here and you can let me know if it
looks better.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
