1 |
Hi all - |
2 |
Ok, here's the deal. I just put 1.0.5.1 into Portage. It has two main |
3 |
shiny bugfixes. Number one being the small typo fix of modules.update to |
4 |
modules-update in default-runscript.sh. The second big fix is that |
5 |
catalyst now detects whether or not baselayout created /dev and |
6 |
populated it. If it did not, catalyst takes care of it. |
7 |
|
8 |
Ok, so baselayout .13-r1 is dead for everything. Use it, and your world |
9 |
will hurt. The current stable bootsplash is -r10, but spock and seemant |
10 |
say that they will get it bumped ASAP (with the 2004.1 graphics even). |
11 |
So, I recommend two things. First, lock baselayout to 1.8.6.13. This can |
12 |
be done by adding the following to your LiveCD spec files: |
13 |
|
14 |
=sys-apps/baselayout-1.8.6.13 |
15 |
|
16 |
If you are building stages, make sure that all other versions of |
17 |
baselayout are masked in your snapshot (you could even lock down the |
18 |
version in your arch's profile). |
19 |
|
20 |
So, since bootsplash is not ready, which means that you cannot make |
21 |
livecds, I recommend that you do the following: |
22 |
|
23 |
1. Test catalyst-1.0.5.1 and mark it stable for your arch. |
24 |
|
25 |
2. Build stages and PackageCDs (remember to use the template linked off |
26 |
of the release guidelines for the PackageCD!!!!!!) |
27 |
Reminder: |
28 |
http://www.gentoo.org/proj/en/releng/docs/packagecd_template.spec.txt |
29 |
|
30 |
3. Work on Release Notes |
31 |
|
32 |
Get those three tasks complete, and 2004.1 will be a snap. Remember to |
33 |
read the release guidelines for QA information!!! |
34 |
|
35 |
Cheers - and thanks for the patience, |
36 |
//zhen |
37 |
-- |
38 |
John Davis |
39 |
Gentoo Linux Developer |
40 |
<http://dev.gentoo.org/~zhen> |
41 |
|
42 |
---- |
43 |
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc> |
44 |
Fingerprint: 2364 71BD 4BC2 705D F338 FF70 6650 1235 1946 2D47 |