Re: r7105 - in trunk/BOOK/stylesheets/lfs-xsl/docbook-xsl-snapshot

2007-09-10 Thread M.Canales.es
El Lunes, 10 de Septiembre de 2007 06:10, Randy McMurchy escribió:

 I'm wondering if we shouldn't go back to using stock stylesheet
 versions installed locally, and not a version included with the sources?

Looks like DB-XSL-1.73.2 is good enough to be used as the default base XSL 
code for the next months (maybe the next upgrade will be to DB-5 + 
DB-XSL-NS-1.74.1, but that is another beast), that is wy I updated the code 
to that release instead to the most current snapshot code.

About going again to system-side installed DB-XSL version, is a matter to 
update the version and instrucctions in the BLFS page, and to install 
DB-XSL-1.73.2 on all servers that are rendering *LFS books, i.e., quantum, 
andiun, and the CLFS servers.

CC to lfs-dev and clfs-dev to let editor and servers admins opine about this.

-- 
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


Re: [Clfs-dev] r7105

2007-09-10 Thread Dan Nicholson
On 9/10/07, Randy McMurchy [EMAIL PROTECTED] wrote:
 Dan Nicholson wrote these words on 09/10/07 12:07 CST:

  Although both methods have their drawbacks, I prefer the current
  method of using a snapshot in the sources. That makes it more robust
  against different hosts since we can enforce the version of the
  stylesheets used.

 Not to argue, but for the sake of discussion, what does different
 hosts have to do with it?

anduin, quantum, my host, your host... If any of us are using
different stylesheets, then we might see different behavior in the
rendered content.

 But more importantly, my point was that placing an entire 3rd party
 package into the (B)LFS sources does not conform to the whole philosophy
 of what our project tries to convey.

That would be the drawback to this approach. If we do go back to using
the host's stylesheets, then it should be completely clear in the
sources (or somewhere else) what version is expected. Possibly we can
check and enforce this in the Makefile.

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page


Re: [Clfs-dev] r7105

2007-09-10 Thread Randy McMurchy
Dan Nicholson wrote these words on 09/10/07 12:26 CST:

 anduin, quantum, my host, your host... If any of us are using
 different stylesheets, then we might see different behavior in the
 rendered content.

But is it *possible* to use different stylesheets? (see below)


 If we do go back to using
 the host's stylesheets, then it should be completely clear in the
 sources (or somewhere else) what version is expected. Possibly we can
 check and enforce this in the Makefile.

I thought it already was. I thought that's what the
xsl:import 
href=http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/docbook.xsl/
(or whatever the relevant version may be) line was for. Have I been
mistaken about this all along?

-- 
Randy

rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
12:39:00 up 6 days, 12:41, 1 user, load average: 0.07, 0.09, 0.13
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page


Re: [Clfs-dev] r7105

2007-09-10 Thread Randy McMurchy
Dan Nicholson wrote these words on 09/10/07 12:07 CST:

 Although both methods have their drawbacks, I prefer the current
 method of using a snapshot in the sources. That makes it more robust
 against different hosts since we can enforce the version of the
 stylesheets used.

Not to argue, but for the sake of discussion, what does different
hosts have to do with it?

But more importantly, my point was that placing an entire 3rd party
package into the (B)LFS sources does not conform to the whole philosophy
of what our project tries to convey.

-- 
Randy

rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
12:15:01 up 6 days, 12:17, 1 user, load average: 0.17, 0.15, 0.17
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page


Re: [Clfs-dev] r7105

2007-09-10 Thread M.Canales.es
El Lunes, 10 de Septiembre de 2007 19:26, Dan Nicholson escribió:

 That would be the drawback to this approach. If we do go back to using
 the host's stylesheets, then it should be completely clear in the
 sources (or somewhere else) what version is expected. Possibly we can
 check and enforce this in the Makefile.

The expected version is defined on the xsl:import statements placed on the top 
level stylesheets/ files (see the LFS-6.2 stylesheets for an example), and a 
sane system must not remap an explicit DB-XSL version to a different one via 
XML catalogs (that is fine for compatible DTDs releases, but never for XSL 
versions), thus that should not be an issue.
 

-- 
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


Re: [Clfs-dev] r7105

2007-09-10 Thread Dan Nicholson
On 9/10/07, M.Canales.es [EMAIL PROTECTED] wrote:
 El Lunes, 10 de Septiembre de 2007 19:26, Dan Nicholson escribió:

  That would be the drawback to this approach. If we do go back to using
  the host's stylesheets, then it should be completely clear in the
  sources (or somewhere else) what version is expected. Possibly we can
  check and enforce this in the Makefile.

 The expected version is defined on the xsl:import statements placed on the top
 level stylesheets/ files (see the LFS-6.2 stylesheets for an example), and a
 sane system must not remap an explicit DB-XSL version to a different one via
 XML catalogs (that is fine for compatible DTDs releases, but never for XSL
 versions), thus that should not be an issue.

My fault. Scratch that comment. I have no objection to using the
host's stylesheets, then.

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page