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
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
|
<?xml version="1.0" encoding="UTF-8"?>
<?python from genshi import HTML ?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:py="http://genshi.edgewall.org/"
xmlns:xi="http://www.w3.org/2001/XInclude"
xml:lang="en" lang="en">
<xi:include href="layout.html" />
<head />
<body>
<leftcontent/>
<div id="centercontent" class="centerfaq">
<h1>packages2.gentoo.org FAQ</h1>
<dl>
<dt class='q'>It broke/doesn't do XYZ! Where do I complain?</dt>
<dd>
Login at the Gentoo Bugzilla, and
<a href="https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Infrastructure&component=packages.gentoo.org&assigned_to=infra-bugs%40gentoo.org">click here</a>.
<br />
If you have a rendering bug in the page, please attach a screenshot.
<br />
If you want a new feature, be sure to read the TODO list first.
</dd>
<dt class="q" id="todo">Short packages2 TODO list</dt>
<dd>
This is not the comprehensive version of the TODO list. <br />
That may be found in the /todo/ directory of the source code.
<ul>
<li>"Search": match a given string against: a substring in packages names, and description</li>
<li>"Similar Packages": same feature from previous version, use the name and description as search data</li>
<li>"Newly Stable": packages that were not in stable in the previous pass, but are now</li>
</ul>
</dd>
<dt class='q'>Where are the RSS feeds?</dt>
<dd>
We decided to go with Atom instead of RSS for this time, but
may add both in future.<br />
For the Atom feeds, the page headers contain a link to the main
feed, as well as a feed specific to the page you are on if
applicable. These feeds are also linked from the bottom of the
right sidebar.<br />
Lastly, the URLs for the feeds of the old packages.gentoo.org
are redirected to the new locations, and will remain redirected
so until August 2009.
</dd>
<dt class='q'>What URLs are available?</dt>
<!-- Please keep this in sync with FRONTEND_FEATURES -->
<dd>
<dl>
<dt><span class="url">/</span></dt>
<dd>All changes</dd>
<dt><span class="url">/categories/</span> <span class="type">[HTML]</span></dt>
<dd>List of categories, with numbers of packages and numbers of ebuilds. <br />
Ordered alphabetically.</dd>
<dt><span class="url">/category/<span class="arg"><name></span></span></dt>
<dd>
Changes in the specified category only.<br />
Ordered by change timestamp, most recent first.<br />
Optional query parameters:
<dl>
<dt><span class="url">?full_cat</span><span class="type">[HTML+RSS]</span></dt>
<dd>Instead of the most recent changes for the category, display all packages, <br />
in alphabetical order. The count parameter is ignored.</dd>
<dt><span class="url">?local_latest</span><span class="type">[HTML]</span></dt>
<dd>Limit the left sidebar to changes in this category only.</dd>
</dl>
</dd>
<dt><span class="url">/package/<span class="arg"><name></span></span></dt>
<dt><span class="url">/package/<span class="arg"><name></span>/<span class="arg"><name></span>[-<span class="arg"><version></span>]</span></dt>
<dd>
Changes for the specified package only.<br />
If no category is provided, any matching package is listed.<br />
You can include a version string for ease of use, but it is ignored.
</dd>
<dt><span class="url">/arch/<span class="arg"><arch></span>[/<span class="arg"><mode></span>]</span></dt>
<dd>
Changes in packages marked with a given architecture only.<br />
Ordered by change timestamp, most recent first.<br />
If it has the keyword, and it is changed, it is included here, regardless of the content of the change.<br />
You may include an optional mode argument:<br />
<dl>
<dt>not specified</dt>
<dd>All changes for the given arch</dd>
<dt>stable</dt>
<dd>Only changed ebuilds with the stable keyword for the arch</dd>
<dt>unstable</dt>
<dd>Only changed ebuilds with the unstable keyword for the arch</dd>
<dt>hardmask</dt>
<dd>Only changed ebuilds that are package.masked on the arch</dd>
</dl>
</dd>
<dt><span class="url">/verbump</span></dt>
<dd>Version bumps only. Please read the note about bump detection.<br />
Ordered by change timestamp, most recent first.
</dd>
<dt><span class="url">/newpackage</span></dt>
<dd>New packages only. Please read the note about bump detection.<br />
Ordered by change timestamp, most recent first.
</dd>
<dt><span class="url">/feed/</span></dt>
<dt><span class="url">/feed/category/<span class="arg"><name></span></span></dt>
<dt><span class="url">/feed/package/<span class="arg"><name></span></span></dt>
<dt><span class="url">/feed/package/<span class="arg"><name></span>/<span class="arg"><name></span>[-<span class="arg"><version></span>]</span></dt>
<dt><span class="url">/feed/arch/<span class="arg"><arch></span>[/<span class="arg"><mode></span>]</span></dt>
<dt><span class="url">/feed/verbump</span></dt>
<dt><span class="url">/feed/newpackage</span></dt>
<dd>
Produce an Atom XML feed of any of the above data pages.<br />
Only the optional query parameters marked with <b>RSS</b> are
accepted by the feeds.<br />
Ordered by change timestamp, most recent first.
</dd>
<dt>Global optional parameters</dt>
<dd>
The URLs above will all accept the following parameters in the query string of the URL.
<dl>
<dt><span class="url">?count=x</span> <span class="type">[HTML+RSS]</span></dt>
<dd>
x: integer between 1 and 200<br />
Allowing to modify count of packages shown in center
</dd>
<dt><span class="url">?left_daycount=x</span> <span class="type">[HTML]</span></dt>
<dd>
x: integer between 1 and 5<br />
When above parameter is set and this parameter too,
daycount on the left can be lowered or raised<br />
(default if unset: 2)
</dd>
<dt><span class="url">?arches=x</span> <span class="type">[HTML]</span></dt>
<dd>
x: one of 'common', 'exotic', 'all', 'prefix', 'linux', 'fbsd'<br />
linux = all Linux arches<br />
prefix = all Prefix arches<br />
fbsd = all FreeBSD arches<br />
all = every arch from the above 3<br />
exotic = Rare Linux arches<br />
common = linux - exotic<br/>
(default if unset: 'common')
</dd>
</dl>
</dd>
</dl>
The dynamic URLs from the old version of the site are not
serviced any more, and using one of them will give you a
redirect to the frontpage. This removes the error-prone parsing
that was used in the previous version of the site. The old
static URLs are forwarded until August 2009 only.
</dd>
<dt class="q">Where is my arch XYZ?</dt>
<dd>
Due to page width constraints, we have broken down the arch
display as follows:<br />
Common: alpha, amd64, arm, hppa, ia64, ppc, ppc64, sparc, x86<br />
Exotic: arm64, mips, m68k, s390, sh, (all of prefix), (all of fbsd)<br />
All: Both sets of arches<br />
If you want to switch between these lists easily, look for the
little C-E-A to the right of the 'Arches' legend.
</dd>
<dt class="q">How does packages2 detect changes?</dt>
<dd>
Because of <a href="https://bugs.gentoo.org/139134">Bug #139134</a>,
tracking the mtimes of the .ebuilds is not a reliable mark of picking
up changed ebuilds.<br />
Instead, we track the checksums of ebuilds and ChangeLogs. If the
checksum on the ChangeLog has changed since the last pass, we
re-read all ebuilds for that package to find the actual changes.
<br />
Additionally, we check for changes in the main package.mask, and
re-compute the keywords affected by those changes.
</dd>
<dt class="q">How does packages2 detect version bumps?</dt>
<dd>
While this isn't a problem while the database is incrementally
updated, it will crop up occasionally if the database is
rebuilt. Version bumps and new packages are detected by the
ebuild or package being present in the current run that were
not present in the previous run. If the database is rebuilt
from empty, the previous run data is not available, so all
packages and ebuilds are considered as new.
</dd>
<dt class="q">Who wrote packages2?</dt>
<dd>
Thanks to the following people for their work on packages2:<br />
<ul>
<li>Markus Ullmann (jokey) - getting the ball rolling on this version</li>
<li>Robin H. Johnson (robbat2) - handling the infra side and lots of coding</li>
<li>Dawid Węgliński (cla) - writing the initial template for packages2</li>
</ul>
</dd>
<dt class="q">Where can I get the source to packages2?</dt>
<dd>
The git tree is available on the Gentoo Git system, with a public read-only copy here: <a href="http://anongit.gentoo.org/#git">http://anongit.gentoo.org/</a>. <br />
The site changelog is located <a href="/media/ChangeLog">here</a>.
</dd>
</dl>
</div>
<rightcontent/>
<footer/>
</body>
</html>
|
GitWeb