[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: D-I Manual on official Debian website [long]



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 16 December 2004 16:06, Frank Lichtenheld wrote:
> > I was thinking of changes that are relevant for Sarge as well.
> > Everybody agrees that the manual for Sarge is far from optimal.
>
> But then these changes should happen in the sarge branch, too. Or you
> have to create a sarge-webpages branch if you want to protect the
> version used in the images from too many changes.

Of course. The question was just: do we want to republish on the web when 
changes in the Sarge branch are made (doesn't have to be for every little 
dotted i or crossed t of course).

> If someone would make a list which packages/versions of packages the
> installmanual needs that aren't available in woody, this would be
> appreciated.

These are the main packages that are required and are known to work:
Package        Sarge version  Woody version
============== ============== ======================
openjade       1.4devel1-13   1.4devel1-8
xsltproc       1.1.8-5        1.0.16-0.2
jadetex        3.13-2.1       3.12-2
docbook        4.3-1          4.1.99really4.2.cr1-2
docbook-xml    4.3-1          4.1.99really4.2.cr1-2
docbook-xsl    1.66.1-1       1.50.0-2
docbook-dsssl  1.79-1         1.76-1
sgml-data      2.0.2          1.5.5
gs-common      0.3.6-0.1      0.3.3.0woody1
w3m            0.5.1-1        0.3-2.4
Note: I have not checked dependencies; also, I could not test everything 
because some steps failed quite early.

I have done a testbuild using Woody, and the results are that _at least_ 
the following packages will need to be backported from Sarge:
- - xsltproc (broken handling of --output option)
- - docbook-xsl (stylesheet errors during build)
- - sgml-data (missing files?)
- - w3m (woody version does not support 'display charset' option)

Also, I got an error from sed in function create-text (when replacing 
unprintable characters) in buildone.sh. That could probably be worked 
around or else a backported version of sed is also required.

In the end I was able to build all formats by using some intermediate 
files build using Sarge.

Cheers,
FJP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBxZqugm/Kwh6ICoQRApQOAJ9f2W4Y0SJxQyPDjQ/WJODJNKG/mQCfc+vF
5s0OsCRYnRgcldGBDq7KzX0=
=vtQK
-----END PGP SIGNATURE-----



Reply to: