1 |
... also known in its former lives as the "Bash Guide" and "The Doc". |
2 |
|
3 |
Ok, I think I've held off announcing this for long enough now. It's not |
4 |
complete, and there's a lot of stuff I'd like to rewrite, but I've been |
5 |
persuaded to announce this anyway on the grounds that some people find |
6 |
it useful and would like to be able to refer to it, even in its |
7 |
unfinished state. Apparently I'm supposed to "release early, release |
8 |
often". |
9 |
|
10 |
What this is: |
11 |
|
12 |
An attempt to document existing Gentoo development practice. The focus |
13 |
is upon 'main tree' things, since that's what I know. The target |
14 |
audience is existing developers and potential recruits -- an existing |
15 |
knowledge of Gentoo from the user perspective is assumed. |
16 |
|
17 |
What this is not: |
18 |
|
19 |
This is not a list of hard rules like, say, the Debian Policy Manual. I |
20 |
personally don't think that that style of hard policy would work for |
21 |
Gentoo. There are exceptions to most rules -- I'm hoping that by |
22 |
explaining the reason behind these rules, rather than just stating "thou |
23 |
shalt not", the reader can get a better idea of when to break the rules |
24 |
and how to do so safely. |
25 |
|
26 |
This is not an official Gentoo thing. It may not mirror Gentoo Policy or |
27 |
the official party line. In some places this is intentional, in others |
28 |
it's a mistake. |
29 |
|
30 |
How it is presented: |
31 |
|
32 |
I'm aiming for a practical approach as far as possible. I've also tried |
33 |
to keep individual sections reasonably separate but with relevant |
34 |
references to other sections. I've tried to use realistic (even real |
35 |
where possible) examples. However, there aren't many nice simple ebuilds |
36 |
in the tree that don't have at least one weird part that would take a |
37 |
lot of irrelevant explanation, so sometimes I've used cut down or made |
38 |
up examples. |
39 |
|
40 |
What still needs doing: |
41 |
|
42 |
Lots. You *will* come across TODO sections, things that aren't well |
43 |
explained, things that need rewriting, things that aren't properly |
44 |
formatted and things that are incorrect. Most sections are about half as |
45 |
big as they need to be to cover everything properly. If you don't like |
46 |
that kind of thing, don't read this. |
47 |
|
48 |
How to contribute: |
49 |
|
50 |
For now, the best way to contribute is to send me text. If you know RST, |
51 |
diffs against the source (link in the page footers) are good. Otherwise, |
52 |
plain text is fine too. I do reserve the right to modify any |
53 |
submissions, but I will of course discuss them with you first if it's |
54 |
anything other than small formatting or wording changes. I might also |
55 |
tell you to go away, but that's fairly unlikely and hasn't happened so |
56 |
far. |
57 |
|
58 |
If you're working on a section or thinking about working on a section, |
59 |
it's probably a good idea to give me a prod first just in case anyone |
60 |
else had the same idea. Sections that already have tentative authors |
61 |
have been marked. |
62 |
|
63 |
Don't ask for the Makefile. Trust me, it's scary, unreliable and you |
64 |
don't want to see it. If I get it to the point where it'll parallel |
65 |
build and work with <bash-3 and <vim-7, I'll post it somewhere. |
66 |
|
67 |
Who to thank: |
68 |
|
69 |
I'd like to thank g2boojum, ka0ttic, rac and slarti for big chunks of |
70 |
content, and agriffis, seemant, azarah, superlag, dmwaters, swift, |
71 |
weeve, jstubbs, ferringb and genone for miscellaneous help along the way |
72 |
(even if some of them didn't realise what they were doing at the time). |
73 |
Also thanks to the various people who have read over parts of it and |
74 |
found some of the many typos and screwups. I've probably forgotten |
75 |
several people -- sorry guys, I'm getting forgetful in my old age. Also |
76 |
thanks to all those people whose ebuilds I nicked. |
77 |
|
78 |
Who not to thank: |
79 |
|
80 |
Uh, you all already know that. |
81 |
|
82 |
Where it is: |
83 |
|
84 |
Obviously, this isn't on Gentoo hardware. For now, it's at the link |
85 |
below. I think the box it's on can cope with serving up static HTML |
86 |
content and a few images (yes, we have images! four of them!), but if |
87 |
not I'll blag some free webspace off someone (probably Berlios) and post |
88 |
an updated URL. |
89 |
|
90 |
http://www.firedrop.org.uk/devmanual/ |
91 |
|
92 |
Sorry, there's no single page version yet. It's something that I could |
93 |
do easily enough with the backend I'm using, but I'm more interested in |
94 |
content for now. |
95 |
|
96 |
Anyway, if you don't like it, feel free to ignore it. Or better yet, |
97 |
post whiny Elmo bitchfest emails about it -- if they're good, I'll print |
98 |
them out and hang them on my wall. |
99 |
|
100 |
|
101 |
-- |
102 |
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools) |
103 |
Mail : ciaranm at gentoo.org |
104 |
Web : http://dev.gentoo.org/~ciaranm |