Re: D-I Manual on official Debian website [long]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 16 December 2004 01:43, Frank Lichtenheld wrote:
> No, this isn't correct. The current structure is
> 1.) releases/stable/releasenotes.<lang>.html
> 2.) releases/stable/installmanual.<lang>.html
> 3.) releases/stable/<arch>/*.<lang>.*
> 4.) releases/stable/<arch>/release-notes.<lang>.*
> 5.) releases/stable/<arch>/release-notes/*.<lang>.html
Hmm. I miss http://www.debian.org/releases/stable/i386/install (same for
other arches) in your list; these are linked from the list at the top of
http://www.debian.org/releases/stable/installmanual and seems to be the
URL where content negotiation takes place. I guess these URLs contain
index.<lang>.html links to the releases/stable/<arch>/install.<lang>.html
files.
> > Note however that currently the build system in that branch does
> > not allow building pdf or txt files.
> > How can we work around this?
>
> merge the change to the branch? I see no way around this.
This will have to be OK'ed by Joey Hess.
> > - - There will probably be major changes to the manual
> > (restructuring) after Sarge is released that are relevant. Do we want
> > to rebuild the manual after release for the website?
>
> We could think about doing that and placing the result in the etch/
> directory.
I was thinking of changes that are relevant for Sarge as well. Everybody
agrees that the manual for Sarge is far from optimal.
Your suggestion would work for any changes in the manual that relate to
post-Sarge changes in the functionality of d-i.
> > - - Should rebuilds (if we want them) be triggered automatically or
> > started manually?
> > What are the implications of this for translations of the website?
> > My preference would be manually because that would make it possible
> > to check the status of translations first and allow to keep the build
> > scripts simpler.
>
> How many people will be able to trigger the build? Hopefully enough...
Depends on where the building process would be hosted and how complex we
make the script. I would suggest keeping the script as simple as possible
and add a README with instructions for publishing the results.
If we decide to build manually I could do the builds at home and make a
tarbal available to d-www people. That should work to start with.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBwUcWgm/Kwh6ICoQRAnbZAJ9zCzm3i2tKr8mm+wZMBD7cTO2uVACgn1SX
akJJMdycXhPOnhk0O4PAD8A=
=zO0i
-----END PGP SIGNATURE-----
Reply to: