Gentoo Archives: gentoo-doc

From: Michael Smith <michael@××××××××.com>
To: gentoo-doc@l.g.o
Subject: [gentoo-doc] Gentoo Best Practices
Date: Tue, 04 Apr 2006 15:41:00
Message-Id: 44329373.3060109@smith-li.com
1 marienz pointed out on #gentoo that there's not much documentation on Gentoo
2 Best Practices. I started to think about what this means.
3
4 In General:
5 I guess "Best Practices" would be stuff that most people already know how to
6 do, but do in different ways. There are more and less "Gentoo-like" ways of
7 doing things. Of course, the docs team may already have a definition for
8 "Gentoo-like", but I suggest it means a more maintainable or more flexible method.
9
10
11 More Specifically:
12 I'm trying to generalize "best practices" here, but first let me get us on the
13 same page by being specific. The topic in question on #gentoo was keyword
14 unmasking. Besides the portage man page and some brief pointers on the wiki,
15 there's not a lot of documentation on the syntax of package.keywords. There are
16 better and worse ways to go about unmasking. One of the worst ways is to use
17 ACCEPT_KEYWORDS. It's difficult to maintain (maximizes your chance of hitting a
18 broken package *or* dep), nearly impossible to reverse, and fairly inflexible
19 in configuration, because it treats every package the same.
20
21 A better way might to use the tilde-version method of keywording for explicitly
22 installed packages, and the plain atom method for keyword-masked dependencies
23 not explicitly in the world file. This method would be flexible (done on a
24 package-by-package basis, with individual dependency control), maintainable (if
25 the explicitly-installed package's stable version is higher than the version
26 number in package.keywords, then the stable version is used, and the
27 dependencies' versions still go no higher than expressed in the explicitly
28 installed package's ebuild), and reversible.
29
30
31 The Point:
32 It's fine if you disagree with that particular suggestion for a best practice
33 the point of this email is to suggest that there ought to be some documentation
34 of best practices. So far the docs team has done a great job of demonstrating
35 how to get things done. The best practices doc could answer those of us who, on
36 occasion wonder *why* we do things a certain way.
37
38
39 What do you think?
40 -Mike
41 --
42 gentoo-doc@g.o mailing list