Gentoo Archives: gentoo-doc

From: Josh Saddler <nightmorph@g.o>
To: gentoo-doc@l.g.o
Cc: gentoo-lists@××××××××××.uk
Subject: Re: [gentoo-doc] Handbooks / Autobuilds: What needs to be done?
Date: Thu, 30 Apr 2009 01:14:34
In Reply to: [gentoo-doc] Handbooks / Autobuilds: What needs to be done? by AllenJB
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] [2] [3]


File name MIME type
signature.asc application/pgp-signature