1 |
Michael Cummings wrote: |
2 |
> So, fellow devs, what's new with development? |
3 |
|
4 |
2007.0 handbooks. I am t3h master of the handbooks. They're basically |
5 |
done, unless I actually hear from arch teams that changes are needed. |
6 |
I've been working my keister off; I think I racked up >100 commits for |
7 |
these things. Part of that was to make future updates easier, as I added |
8 |
conditional evaluations to all the handbooks. This lets an editor make a |
9 |
single small change to the ToC for some $arch handbook (say, to use a |
10 |
new kernel version), and those changes will be propagated to every |
11 |
chapter of that arch HB. Lots of XML <keyval> and <keys> now used for |
12 |
all arches. |
13 |
|
14 |
Also, I'm looking into redoing how the handbooks are done in the first |
15 |
place; right now, we have vast amounts of shared content that are |
16 |
identical between arches, but are still repeated in each |
17 |
hb-install-$arch-bootloader.xml file, for example. The existing setup: |
18 |
within those pages, we can display extra content (or avoid displaying |
19 |
content) just by doing an XML test to see which handbook you are viewing |
20 |
(i.e. if you view Sparc, you won't see the x86 partitioning scheme). |
21 |
|
22 |
I sent a proposal to the gentoo-doc list about turning that on its head, |
23 |
and instead using several more separate files that include that shared |
24 |
content, so that we can cut down the duplications in the $arch-foo.xml |
25 |
files through the use of <include/>s that would pull in that shared |
26 |
content. End result is that you'd end up with a very trimmed down file |
27 |
that only includes extra content relevant to that arch, with GuideXML |
28 |
mojo to yank in the non-arch-specific content. Nifty, eh? |