M.Canales.es wrote: > Matthew Burgess escribi� en blfs.dev el S�bado, 19 de Marzo de 2005 10:43: > > > >>Actually Randy, if I understand Manuel correctly, the package should >>only be considered "broken" if it references 'current' *and* it >>customises the stylesheets (due to customisation parameters changing >>between versions, etc.). If gtk-doc does no such customisation, then >>you should be fine putting the 'current' link in the book, and I'd be as >>bold as to suggest it goes in the 'xsl-stylesheets' instructions. > > > > Correct. For XSL to remap "current" to the most newest version is fine. > "current" is used when processing XML docs using the stock XSL release. > > What is wrong is to remap an old XSL version to a new one (like the remap of > 1.65.1 to 1.67.2 in BLFS), due that harcoded XSL versions are found tipically > in customized templates, that relies upon that concret XSL version and may not > work well with a new one. > >
So we really do need to rip out that rewrite and suggest that 1.65.1 is installed along side it then, correct? And then add the current rewrite to xsl instructions. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
