From: Josh Saddler <nightmorph@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Cc: gentoo-lists@allenjb.me.uk
Subject: Re: [gentoo-doc] Handbooks / Autobuilds: What needs to be done?
Date: Wed, 29 Apr 2009 18:14:27 -0700 [thread overview]
Message-ID: <49F8FB73.7050308@gentoo.org> (raw)
In-Reply-To: <49F58781.9090606@allenjb.me.uk>
[-- Attachment #1: Type: text/plain, Size: 2869 bytes --]
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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-04-30 1:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 10:22 [gentoo-doc] Handbooks / Autobuilds: What needs to be done? AllenJB
2009-04-30 1:14 ` Josh Saddler [this message]
2009-04-30 14:52 ` Ben de Groot
2009-04-30 15:29 ` Nathan Zachary
2009-04-30 20:29 ` Josh Saddler
2009-04-30 21:07 ` Nathan Zachary
2009-04-30 22:27 ` Josh Saddler
2009-04-30 23:21 ` Nathan Zachary
2009-05-01 0:41 ` wireless
2009-05-01 8:13 ` Ben de Groot
2009-05-01 11:30 ` [gentoo-doc] " Duncan
2009-05-01 11:44 ` AW: " KKH
2009-05-01 18:30 ` Марьясин Семён
2009-04-30 20:45 ` [gentoo-doc] " Joseph Jezak
2009-04-30 20:54 ` Josh Saddler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F8FB73.7050308@gentoo.org \
--to=nightmorph@gentoo.org \
--cc=gentoo-doc@lists.gentoo.org \
--cc=gentoo-lists@allenjb.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox