Prelink documentation system appears to be obsolete.

Prelink documentation system appears to be obsolete.

[Scott Garman]

 From my attempts to get documentation building correctly for prelink, 
it's becoming clear to me that the package's documentation system uses a 
number of deprecated teTeX elements and needs updating at a "big 
picture" level. From what I understand, TeXLive is the new hotness and 
requires some migration.

In doc/prelink.tex, build errors lead me to suggest the following changes:

Change \usepackage{fancyheadings} to \usepackage{fancyhdr}:
http://us.generation-nt.com/bug-421071-ftbfs-latex-error-file-fancyheadings-sty-not-found-help-164921921.html

Change [make|print]glossary to [make|print]nomenclature:
http://pleasemakeanote.blogspot.com/2009/02/latex-undefined-control-sequence.html

Don't define \ifpdf manually, \usepackage{ifpdf}:
http://old.nabble.com/Package-ifpdf-error:-name-clash---%5Cifpdf-is-already-defined-td18730554.html

After resolving these issues, I still end up with a failure building the 
docs - but this time there's no clear error message to give me clues on 
what needs fixing. My gut feeing is that the migration process from 
teTeX to TeXLive needs to be done by someone more familiar with it than I.

Until that happens (or I suddenly become a TeX guru), I'm currently 
advising that we keep the workaround in the prelink recipe which 
prevents documentation from being built. Then I can move on to 
addressing documentation builds in other packages.

Scott

-- 
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
Intel Open Source Technology Center

Re: Prelink documentation system appears to be obsolete.

[Mark Hatle]

On 2/8/11 6:35 PM, Scott Garman wrote:
>  From my attempts to get documentation building correctly for prelink, 
> it's becoming clear to me that the package's documentation system uses a 
> number of deprecated teTeX elements and needs updating at a "big 
> picture" level. From what I understand, TeXLive is the new hotness and 
> requires some migration.
> 
> In doc/prelink.tex, build errors lead me to suggest the following changes:
> 
> Change \usepackage{fancyheadings} to \usepackage{fancyhdr}:
> http://us.generation-nt.com/bug-421071-ftbfs-latex-error-file-fancyheadings-sty-not-found-help-164921921.html
> 
> Change [make|print]glossary to [make|print]nomenclature:
> http://pleasemakeanote.blogspot.com/2009/02/latex-undefined-control-sequence.html
> 
> Don't define \ifpdf manually, \usepackage{ifpdf}:
> http://old.nabble.com/Package-ifpdf-error:-name-clash---%5Cifpdf-is-already-defined-td18730554.html
> 
> After resolving these issues, I still end up with a failure building the 
> docs - but this time there's no clear error message to give me clues on 
> what needs fixing. My gut feeing is that the migration process from 
> teTeX to TeXLive needs to be done by someone more familiar with it than I.
> 
> Until that happens (or I suddenly become a TeX guru), I'm currently 
> advising that we keep the workaround in the prelink recipe which 
> prevents documentation from being built. Then I can move on to 
> addressing documentation builds in other packages.

The prelink documentation (other then man pages) is identical to the upstream
project.  So my suggestion [if we do fix the docs] is to push it upstream first
(or attempt to) then in my regular syncs I'll pull it back down.

The man pages do have some local changes to document the additional arguments
introduce by the cross friendly version of prelink.

--Mark