Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-doc
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-doc@g.o
From: Josh Saddler <nightmorph@g.o>
Subject: Re: Handbooks / Autobuilds: What needs to be done?
Date: Wed, 29 Apr 2009 18:14:27 -0700
AllenJB wrote:
> Hi all,
> 
> Is there a breakdown of tasks for updating the handbooks for autobuilds?
> I looked at bug #260403 but it doesn't seem to say what actually needs
> to be done (I also browsed through the other open docs bugs and there's
> barely anything related to the user handbook there).

This is something that I've brought up on this list all the way back at
the beginning of March[1]. Someone else raised the issue earlier this
month[2].

As of right now, no one's bothered to reply on the list, nor respond
when I jump on to our IRC channel.

For the record, I have updated /main/en/where.xml for bug 266464[3].

But as I'm the only one doing any work these days, I have no idea when
the rest might be completed. As far as I know I'm the only one to even
start to consider all the things that need to be changed.

A few off the top of my head:

1. Keys in handbook-$arch.xml files
- No longer need paths to point releases. Update paths to install media
on the mirrors.
- Kernel versions will change fairly rapidly with the autobuilds, even
though the stages only have stable kernels.
- Keep monitoring ISO/stage size, or else discard keeping this
information, which is already present in /main/en/where.xml. I'm in
favor of just using a range of MB, rather than a specific size. Means
less constant updating.
- Recommended CFLAGS, especially now that GCC 4.3 is stable. Includes
new arches for e.g. C2D, new arches that superset things. Better yet,
what about just using -march=native? Native detects what you have and
sets based on that.

2. Various renames that have happened now that we no longer do point
releases.

3. Handbook restructuring proposal. I've sent some variants to the list
a few times now, what with the lack of point releases for networked and
networkless media. Needs some rethinking, and though I could just
unilaterally *do something* (again, no one else is doing work), I need
the rest of the team involved. Plus our leader should sign off on any
big changes.
- Maybe just provide some kind of current-networked and
current-networkless link/symlink/directory? Similar to what the
autobuilds have. There's no longer a need to track a specific
networkless revision, not even as an archive, as the old files are not
preserved past a certain point.
- Some arches have build trouble at the moment, and do not provide
updated CDs (yet). This may require mixing and matching directions and
install media.
- More arches are adding autobuilds, including ARM, alpha, hppa. Must
update as these become available.

4. ???

5. Profit.

That's it for now, I guess.

[1]
http://archives.gentoo.org/gentoo-doc/msg_4db815c5379134f5047b268361977b3d.xml
[2]
http://archives.gentoo.org/gentoo-doc/msg_498f230e6f69df9091b8b2b1d39ce0fb.xml
[3] http://bugs.gentoo.org/266464


Attachment:
signature.asc (OpenPGP digital signature)
Replies:
Re: Handbooks / Autobuilds: What needs to be done?
-- Joseph Jezak
Re: Handbooks / Autobuilds: What needs to be done?
-- Ben de Groot
References:
Handbooks / Autobuilds: What needs to be done?
-- AllenJB
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Handbooks / Autobuilds: What needs to be done?
Next by thread:
Re: Handbooks / Autobuilds: What needs to be done?
Previous by date:
Handbooks / Autobuilds: What needs to be done?
Next by date:
Re: Handbooks / Autobuilds: What needs to be done?


Updated Jun 17, 2009

Summary: Archive of the gentoo-doc mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.