blob: 1baee354c1dab9bb00f8cc563c7e9c72bee8cb17 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
ebuild_q1:
title: Big changes in Gentoo
documentation: GLEPs
categories: [ebuild]
content: What is the proper method for suggesting a wide-ranging feature
or enhancement to Gentoo? Describe the process for getting this feature
approved and implemented.
ebuild_q2:
title: Responsibilities
documentation: devrel policy
categories: [ebuild]
content: Who should be contacted with complaints about specific developers
or projects?
ebuild_q3:
title: Gentoo mailing lists
documentation: gentoo.org
categories: [ebuild]
content: "When is it appropriate to post to the following mailing lists:
gentoo-core, gentoo-dev, gentoo-dev-announce, gentoo-project?"
ebuild_q4:
title: src_install
documentation: GLEPs
categories: [ebuild]
question_group: ebuild_group1
content: "\n src_install () {
\n dobin uvconvert/${PN}
\n doman uvconv.1
\n dodoc readme.txt AUTHORS CREDITS changes.txt
\n }"
ebuild_q5:
title: src_install
documentation: devmanual
categories: [ebuild]
question_group: ebuild_group1
content: "\n src_install() {
\n dobin utrac
\n doman utrac.1
\n dodoc README CHANGES CREDITS
\n }"
ebuild_q6:
title: src_install
documentation: handbook
categories: [ebuild]
question_group: ebuild_group1
content: "\n src_install() {
\n dobin tree
\n doman man/tree.1
\n dodoc CHANGES README*
\n }"
mentor_q1:
title: Scopes in ebuild
documentation: handbook
categories: [mentoring]
content: "What's the difference between local and global scope in an ebuild?"
mentor_q2:
title: Optional SSL support in ebuild
documentation: devmanual
categories: [mentoring]
content: 'You have a patch for foomatic which enables SSL support that is
optional at build time. Assuming that foomatic uses an autotools based
build system provide most probable changes required in an `EAPI="0"` ebuild.
What should be done for the ebuild in case it uses `EAPI="2"`?'
mentor_q3:
title: Improve maintainability of ebuild
documentation: devmanual
categories: [mentoring]
content: "You are writing an ebuild for the foomatic package. Upstream calls
the current version \"1.3-7b\" (but this is _not_ a beta release). How would the
ebuild be named? What's wrong with the ebuild snippet below and how should this
be written to aid maintainability?
\n\n SRC_URI=\"http://foomatic.example.com/download/foomatic-1.3-7b.tar.bz2\"
\n S=${WORKDIR}/foomatic-1.3-7b"
non_q1:
title: Gentoo Foundation
documentation: gentoo.org
categories: [non_ebuild]
content: What is the Gentoo Foundation? How does one apply for
membership and who are eligible?
non_q2:
title: Gentoo Council
documentation: GLEPs
categories: [non_ebuild]
content: What is the purpose of the Gentoo Council?
|
GitWeb