El Martes, 11 de Septiembre de 2007 15:04, Alexander E. Patrakov escribió:
> OK. Now imagine the following situation: someone wants to create a > Debian package with the LFS book. Debian policy requires that all HTML > and PDF files are rebuilt from XML source in this case. If the LFS book > relies on the external DocBook XSL setup of a certain version, I see no > way to do it, except by reverting the switch to the external copy of > DocBook XSL stylesheets (which is as bad as any other reversion of > upstream changes) or changing the stylesheet version to "current" (which > is going to break PDF - even worse). I don't see here an issue for us, but for distro packages creators. In any distro, when package A depend on version X of package B where X is not the default version for B on the target distro release version, then a package B-X that can be installed side-by-side without conflicts with the default package B is created. That has been true from always for autotools packages, back-ward compatibility libraries, libstdc++ versions needed to run closed binaries, etc. Why should it be diferent when related about DB-XSL versions? -- Manuel Canales Esparcia Usuario de LFS nº2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
