1 |
Hello all, |
2 |
|
3 |
This is a text-only version of the Gentoo/AMD64 Project Status Report, which is |
4 |
also accessible here: |
5 |
|
6 |
http://www.gentoo.org/proj/en/base/amd64/status/status_20060110.xml |
7 |
|
8 |
================================== |
9 |
Gentoo/AMD64 Project Status Report |
10 |
================================== |
11 |
|
12 |
This is the status of the Gentoo/AMD64 Project. It will be posted regularly, but |
13 |
not with a static frequency. All questions can be posted to amd64@g.o. |
14 |
|
15 |
This status report is mainly concerned about the progress made between Jan 1, |
16 |
2005 and Dec 31, 2005. |
17 |
|
18 |
Status Report in Figures |
19 |
```````````````````````` |
20 |
|
21 |
* 1'486 bugs assigned to amd64@g.o [1] and amd64-test@g.o [2] were |
22 |
fixed. |
23 |
* The Gentoo/AMD64 team [3] has grown from 9 developers to 32 developers. Also, |
24 |
we have our own arch testers team [4] which counts 16 active volunteers. |
25 |
* Two full releases and one media refresh release were made. |
26 |
|
27 |
Release Engineering |
28 |
``````````````````` |
29 |
|
30 |
In March 2005, a major step towards true multilib support was made when |
31 |
releasing 2005.0. Starting from this release, the `multilib` USE flag, mainly |
32 |
used by the toolchain packages, was deprecated and instead, subprofiles should |
33 |
be used to control the behaviour regarding multilib-support. |
34 |
As a consequence of this change, the `sys-libs/glibc` package now builds |
35 |
natively both 64bit and 32bit version and the precompiled |
36 |
`app-emulation/emul-linux-x86-glibc` package is no longer needed. |
37 |
The change also enabled a far easier way to track dependencies for 32bit |
38 |
packages through `multilib.eclass` that was written. |
39 |
With 2005.0 and the profile change, a new feature called `multilib-strict` was |
40 |
introduced. It is a QA tool to assure that all packages install their libraries |
41 |
into the correct directories, which is essential for multilib systems. |
42 |
To make the complicated upgrade process easier for users, automated scripts and |
43 |
detailed documentation were provided. |
44 |
|
45 |
In August 2005, Gentoo 2005.1 was released. New stages and CDs were made and the |
46 |
default USE flags were reviewed and cut down to a minimum. |
47 |
|
48 |
In November, a media refresh release called 2005.1-r1 was made. It was mainly a |
49 |
bugfix release to fix a few bugs in the stages and CDs, the 2005.1 profile was kept. |
50 |
|
51 |
Stable-profile |
52 |
`````````````` |
53 |
|
54 |
As AMD64 processors became a lot cheaper, its popularity grew enormously. Thanks |
55 |
to the stable-profile- and AT-project we could ensure that the AMD64 stable |
56 |
profile was always up to date and almost as recent as the x86 one. |
57 |
|
58 |
Documentation |
59 |
````````````` |
60 |
|
61 |
The documentation subproject has written multiple new documents: |
62 |
|
63 |
* The Gentoo/AMD64 FAQ [5] |
64 |
* The 2005.0 Upgrade Guide [6] |
65 |
* Howto file bugs [7] |
66 |
* 32bit Chroot Guide for Gentoo/AMD64 [8] |
67 |
* The Gentoo/AMD64 Testing Docs [9] |
68 |
* Arch Specific Notes -- AMD64/EM64T [10] |
69 |
|
70 |
Since these documents cover almost all aspects of a amd64 system, the old |
71 |
technotes [11] could be deprecated. |
72 |
|
73 |
Further, a list [12] was put together to document the emulation packages, mainly |
74 |
to assure that vulnerabilities also get fixed in the pre-compiled |
75 |
`emul-linux-x86-*` packages. |
76 |
|
77 |
Gentoo/AMD64 Arch Testers |
78 |
````````````````````````` |
79 |
|
80 |
The Gentoo/AMD64 Arch Testers subproject was founded to recruit more developers |
81 |
and power-users which could help to reduce the workload significantly. The idea |
82 |
turned out to be a great success: Over 25 ATs [4] were recruited of which 6 |
83 |
became developers. To make the testing and keywording even more efficient, GLEP |
84 |
41 [13] was brought up. |
85 |
|
86 |
Donations |
87 |
````````` |
88 |
|
89 |
We got multiple boxes donated by AMD, which are now mainly used to offer shell |
90 |
accounts to other Gentoo developers that want to test their patches before |
91 |
committing them. They're also used as distcc nodes to speed up the release |
92 |
engineering tasks. |
93 |
|
94 |
References: |
95 |
[1] mailto:amd64@g.o |
96 |
[2] mailto:amd64-test@g.o |
97 |
[3] http://www.gentoo.org/proj/en/base/amd64/#Developers |
98 |
[4] http://www.gentoo.org/proj/en/base/amd64/tests/index.xml?part=1&chap=1#doc_chap1 |
99 |
[5] http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml |
100 |
[6] http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=1 |
101 |
[7] http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 |
102 |
[8] http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=3 |
103 |
[9] http://www.gentoo.org/proj/en/base/amd64/tests/index.xml |
104 |
[10] http://dev.gentoo.org/~plasmaroo/devmanual/archs/amd64/ |
105 |
[11] http://www.gentoo.org/proj/en/base/amd64/technotes/index.xml |
106 |
[12] http://www.gentoo.org/proj/en/base/amd64/emul/emul-content.txt |
107 |
[13] http://www.gentoo.org/proj/en/glep/glep-0041.html |
108 |
|
109 |
-- |
110 |
Simon Stelling |
111 |
Gentoo/AMD64 Operational Co-Lead |
112 |
blubb@g.o |
113 |
-- |
114 |
gentoo-amd64@g.o mailing list |