M.Canales.es wrote these words on 07/04/07 15:34 CST:
> 1. - Wait up to the next *.1 release to start using the new code. That could
> meant to wait at least other 3-4 months :-/
>
> 2.- To create our own LFS-XSL-1.0 package based on current new-xsl branch
> code and use it as a temporally solution. That implies to add a installation
> page for such package in BLFS and to install it on the servers and editor's
> machines.
>
> 3.- To clean-up the docbook-xsl-snapshoot branch subdirectory to keep only
> that files actualy required to build the books. Then merge the code to the
> {,B,C,H}LFS SVN trees. That will made the book's sources full auto-contained.
> This will increase maintenance work to keep it sinchronized with upstream
> code, but IMHO is the more simple solution and my prefered way.
Since Manuel is the one doing all the work, I defer my vote to
whichever option he wants (#3). This way we can keep the new version
of FOP in the book, or at least not have to put the previous version
in as well.
--
Randy
rmlscsi: [bogomips 1003.28] [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]
16:04:00 up 6 days, 13:55, 1 user, load average: 0.10, 0.14, 0.09
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
