Gentoo Archives: gentoo-dev

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