Fontconfig/DocBook-utils issue

[LFS-User@…]

If you remove the --disable-docs parameter from configure in the Fontconfig instructions to use DocBook-utils, you must now also have JadeTeX installed of the build will fail during the building of the PDF documentation.

I'm not sure if this is new to this release, or what, but we need to document it just like the SGMLSpm stuff is documented. What might be best is to parenthesize the need for the JadeTeX and SGMLSpm packages as mandatory in the DocBook-utils dependency. In other words, the optional dependency must say that DocBook-utils (and all its dependencies) are required to build the documentation.

Or, simply remove DocBook-Utils as a dependency and don't mention anything so that folks will always use the --disable-docs parameter as outlined in the book.

[LFS-User@…]

Decided to just clean up the text and make it clear what needs to be installed if you wish to build the docs.

[LFS-User@…]

Clarified the DocBook-utils dependencies.

[LFS-User@…]

Reopening bug as there is confirmed breakage in the build commands. This needs to be fixed before releasing 6.1.

If you have DocBook-utils installed, but not JadeTeX, the 'make -C doc install' command will fail.

My suggestion is to remove the 'make -C doc install' command and replace it with hand-installation.

I will rename my docbook2html command (what configure looks for to determine if DocBook-utils is installed) and run the 'make -C doc install' command to determine where everything is installed, so we can match it.

[LFS-User@…]

Modified Fontconfig documentation installation so that it will always work by using install commands instead of 'make -C doc install'

Leaving the bug open until Bruce merges the changes into the 6.1 branch (r4899)

[bdubbs@…]

Merged chages from Fontconfig into 6.1-pre2.

[(none)]

Milestone 6.1 deleted