[gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: faq.xml - gentoo-commits

From:	"Jeremy Olexa (darkside)" <darkside@g.o>
To:	gentoo-commits@l.g.o
Subject:	[gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: faq.xml
Date:	Thu, 09 Oct 2008 20:33:17
Message-Id:	`E1Ko2C9-0007bg-MN@stork.gentoo.org`

1

darkside    08/10/09 20:33:13

2

3

  Added:                faq.xml

4

  Log:

5

  Add new faq.xml doc written by myself

6

7

Revision  Changes    Path

8

1.1                  xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml

9

10

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml?rev=1.1&view=markup

11

plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml?rev=1.1&content-type=text/plain

12

13

Index: faq.xml

14

===================================================================

15

<?xml version="1.0" encoding="UTF-8"?>

16

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml,v 1.1 2008/10/09 20:33:13 darkside Exp $: -->

17

<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>

18

<!DOCTYPE guide SYSTEM "http://www.gentoo.org/dtd/guide.dtd">

19

20

<guide link="/proj/en/gentoo-alt/prefix/faq.xml" lang="us">

21

<title>Frequently Asked questions about the Gentoo Prefix Project</title>

22

23

<author title="Author">

24

  <mail link="darkside@g.o">Jeremy Olexa</mail>

25

</author>

26

<abstract>

27

This guide covers questions frequently asked by users of Gentoo Prefix

28

</abstract>

29

30

<!-- The content of this document is licensed under the CC-BY-SA license -->

31

<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->

32

<license/>

33

34

<version>1.0</version>

35

<date>2008-10-09</date>

36

37

<chapter>

38

<title>Gentoo Prefix Frequently Asked Questions</title>

39

  <section>

40

    <title>How can I contribute?</title>

41

    <body>

42

<p>

43

    Due to the depth of the Gentoo Prefix project, we really like to have users

44

    become involved. It helps us immensely. Here are some possibilities:

45

  	</p>

46

    <ul>

47

      <li>

48

      Report bugs! Unreported bugs are very bad for the health of the

49

      project, please do report bugs

50

      </li>

51

      <li>

52

      Report working packages that you may have <uri

53

      link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/ecopy.xml">imported</uri>

54

      </li>

55

      <li>

56

      Test packages - We cannot make sure that every package on every arch works

57

      by ourselves.

58

      </li>

59

      <li>

60

      Bootstrapping must always work, rebootstrapping often and reporting issues

61

      would benefit all and you might learn something as well.

62

      </li>

63

    </ul>

64

    </body>

65

  </section>

66

67

  <section>

68

  <title>I made a fix, what is the best way to report this?</title>

69

  <body>

70

<p>

71

  The absolute best way to report fixes is through <uri

72

  link="https://bugs.gentoo.org/">Gentoo's Bugzilla.</uri> Use the

73

  "Gentoo/Alt" Product with the "Prefix Support" component, or click <uri

74

  link="https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%2FAlt">here</uri>.

75

  The second best way is two report them on the gentoo-alt <uri

76

  link="http://www.gentoo.org/main/en/lists.xml">mailing list</uri>, however, 

77

  items may get forgotten or overlooked on the mailing list. Finally, you may

78

  report items in irc, but be sure you are speaking to a Gentoo Prefix

79

  developer, otherwise it is likely to not be noticed.

80

  </p>

81

  </body>

82

  </section>

83

84

  <section>

85

  <title>XXX ebuild works for me, now what?</title>

86

  <body>

87

<p>

88

  Please report it! See above and also see <uri

89

  link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/ecopy.xml#doc_chap2">here</uri>

90

  </p>

91

  </body>

92

  </section>

93

94

  <section>

95

  <title>I want to run Gentoo Prefix within my company, am I allowed to do so?</title>

96

  <body>

97

<p>

98

  Of course, see above for support ;) Also, you must obey whichever license as

99

  applies.

100

  </p>

101

  </body>

102

  </section>

103

104

  <section>

105

  <title>How mature is Gentoo Prefix?</title>

106

  <body>

107

<p>

108

  Many of us use Gentoo Prefix everyday and it has been in existance since

109

  2004. Keep in mind that you are riding the tip of the portage code and the

110

  latest packages as they exist in the gentoo-x86 tree.

111

112

  Gentoo Prefix is believed to have a reasonable maturity. However, as always,

113

  our software comes without warranty.

114

  </p>

115

  </body>

116

  </section>

117

118

  <section>

119

  <title>What is the "gentoo-x86 tree" ?</title>

120

  <body>

121

<p>

122

  gentoo-x86 is what Gentoo Linux calls their tree that contains all the

123

  ebuilds. See <uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/">

124

  here.</uri>

125

  </p>

126

  </body>

127

  </section>

128

129

  <section>

130

  <title>On which platforms does Gentoo Prefix run on?</title>

131

  <body>

132

<p>

133

  Many platforms, including but not limited to: RHEL, SLES, HP-UX, AIX, Solaris,

134

  OS X, Interix (SFU on Windows).

135

  </p>

136

  </body>

137

  </section>

138

139

  <section>

140

  <title>What is the best way to contact a Gentoo Prefix developer?</title>

141

  <body>

142

<p>

143

  Please do not send us unsolicited mail. We prefor to receive list mail.

144

  See above for info on the gentoo-alt mailing list.

145

  </p>

146

  </body>

147

  </section>

148

149

  <section>

150

  <title>I want to import an ebuild, how do I go about that?</title>

151

  <body>

152

<p>

153

  <uri

154

  link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/ecopy.xml">Documentation</uri>

155

  already exists.

156

  </p>

157

  </body>

158

  </section>

159

160

  <section>

161

  <title>I want to uninstall Gentoo Prefix from my system, how?</title>

162

  <body>

163

<p>

164

  rm -rf "${EPREFIX}" 

165

  </p>

166

  </body>

167

  </section>

168

169

  <section>

170

  <title>I don't understand something in this FAQ!</title>

171

  <body>

172

  <p>Please join #gentoo-alt on irc.gentoo.org or utilize the gentoo-alt

173

  mailing list.

174

  </p>

175

  </body>

176

  </section>

177

178

</chapter>

179

</guide>

180

181

<!-- vim: set expandtab ts=2 sw=2 foldmethod=marker foldenable: -->

1	darkside 08/10/09 20:33:13
2
3	Added: faq.xml
4	Log:
5	Add new faq.xml doc written by myself
6
7	Revision Changes Path
8	1.1 xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml
9
10	file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml?rev=1.1&view=markup
11	plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml?rev=1.1&content-type=text/plain
12
13	Index: faq.xml
14	===================================================================
15	<?xml version="1.0" encoding="UTF-8"?>
16	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/faq.xml,v 1.1 2008/10/09 20:33:13 darkside Exp $: -->
17	<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
18	<!DOCTYPE guide SYSTEM "http://www.gentoo.org/dtd/guide.dtd">
19
20	<guide link="/proj/en/gentoo-alt/prefix/faq.xml" lang="us">
21	<title>Frequently Asked questions about the Gentoo Prefix Project</title>
22
23	<author title="Author">
24	<mail link="darkside@g.o">Jeremy Olexa</mail>
25	</author>
26	<abstract>
27	This guide covers questions frequently asked by users of Gentoo Prefix
28	</abstract>
29
30	<!-- The content of this document is licensed under the CC-BY-SA license -->
31	<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
32	<license/>
33
34	<version>1.0</version>
35	<date>2008-10-09</date>
36
37	<chapter>
38	<title>Gentoo Prefix Frequently Asked Questions</title>
39	<section>
40	<title>How can I contribute?</title>
41	<body>
42	<p>
43	Due to the depth of the Gentoo Prefix project, we really like to have users
44	become involved. It helps us immensely. Here are some possibilities:
45	</p>
46	<ul>
47	<li>
48	Report bugs! Unreported bugs are very bad for the health of the
49	project, please do report bugs
50	</li>
51	<li>
52	Report working packages that you may have <uri
53	link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/ecopy.xml">imported</uri>
54	</li>
55	<li>
56	Test packages - We cannot make sure that every package on every arch works
57	by ourselves.
58	</li>
59	<li>
60	Bootstrapping must always work, rebootstrapping often and reporting issues
61	would benefit all and you might learn something as well.
62	</li>
63	</ul>
64	</body>
65	</section>
66
67	<section>
68	<title>I made a fix, what is the best way to report this?</title>
69	<body>
70	<p>
71	The absolute best way to report fixes is through <uri
72	link="https://bugs.gentoo.org/">Gentoo's Bugzilla.</uri> Use the
73	"Gentoo/Alt" Product with the "Prefix Support" component, or click <uri
74	link="https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%2FAlt">here</uri>.
75	The second best way is two report them on the gentoo-alt <uri
76	link="http://www.gentoo.org/main/en/lists.xml">mailing list</uri>, however,
77	items may get forgotten or overlooked on the mailing list. Finally, you may
78	report items in irc, but be sure you are speaking to a Gentoo Prefix
79	developer, otherwise it is likely to not be noticed.
80	</p>
81	</body>
82	</section>
83
84	<section>
85	<title>XXX ebuild works for me, now what?</title>
86	<body>
87	<p>
88	Please report it! See above and also see <uri
89	link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/ecopy.xml#doc_chap2">here</uri>
90	</p>
91	</body>
92	</section>
93
94	<section>
95	<title>I want to run Gentoo Prefix within my company, am I allowed to do so?</title>
96	<body>
97	<p>
98	Of course, see above for support ;) Also, you must obey whichever license as
99	applies.
100	</p>
101	</body>
102	</section>
103
104	<section>
105	<title>How mature is Gentoo Prefix?</title>
106	<body>
107	<p>
108	Many of us use Gentoo Prefix everyday and it has been in existance since
109	2004. Keep in mind that you are riding the tip of the portage code and the
110	latest packages as they exist in the gentoo-x86 tree.
111
112	Gentoo Prefix is believed to have a reasonable maturity. However, as always,
113	our software comes without warranty.
114	</p>
115	</body>
116	</section>
117
118	<section>
119	<title>What is the "gentoo-x86 tree" ?</title>
120	<body>
121	<p>
122	gentoo-x86 is what Gentoo Linux calls their tree that contains all the
123	ebuilds. See <uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/">
124	here.</uri>
125	</p>
126	</body>
127	</section>
128
129	<section>
130	<title>On which platforms does Gentoo Prefix run on?</title>
131	<body>
132	<p>
133	Many platforms, including but not limited to: RHEL, SLES, HP-UX, AIX, Solaris,
134	OS X, Interix (SFU on Windows).
135	</p>
136	</body>
137	</section>
138
139	<section>
140	<title>What is the best way to contact a Gentoo Prefix developer?</title>
141	<body>
142	<p>
143	Please do not send us unsolicited mail. We prefor to receive list mail.
144	See above for info on the gentoo-alt mailing list.
145	</p>
146	</body>
147	</section>
148
149	<section>
150	<title>I want to import an ebuild, how do I go about that?</title>
151	<body>
152	<p>
153	<uri
154	link="http://www.gentoo.org/proj/en/gentoo-alt/prefix/ecopy.xml">Documentation</uri>
155	already exists.
156	</p>
157	</body>
158	</section>
159
160	<section>
161	<title>I want to uninstall Gentoo Prefix from my system, how?</title>
162	<body>
163	<p>
164	rm -rf "${EPREFIX}"
165	</p>
166	</body>
167	</section>
168
169	<section>
170	<title>I don't understand something in this FAQ!</title>
171	<body>
172	<p>Please join #gentoo-alt on irc.gentoo.org or utilize the gentoo-alt
173	mailing list.
174	</p>
175	</body>
176	</section>
177
178	</chapter>
179	</guide>
180
181	<!-- vim: set expandtab ts=2 sw=2 foldmethod=marker foldenable: -->

Gentoo Archives: gentoo-commits