10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
12.2
12.2-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v3_0
v3_1
v3_2
v3_3
v4_0
v4_1
v5_0
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/loongarch-12.2
xry111/mips64el
xry111/multilib
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
Line | |
---|
1 | How to edit the LFS-BOOK
|
---|
2 | ------------------------
|
---|
3 |
|
---|
4 | This document explains the necessary steps to be taken in order to make
|
---|
5 | changes to the LFS-BOOK. Not every single aspect is detailed, just the
|
---|
6 | more tricky ones.
|
---|
7 |
|
---|
8 | * No matter what, always make the following changes whenever you do
|
---|
9 | something:
|
---|
10 |
|
---|
11 | Whenever you make a change, no matter how small, update the book's version
|
---|
12 | number:
|
---|
13 |
|
---|
14 | 1) Open the index.xml file.
|
---|
15 |
|
---|
16 | 2) Find <!ENTITY version "yyyymmdd"> and make sure it contains the date on
|
---|
17 | which you are making the change. If today is June 11th, 2001, change it
|
---|
18 | to <!ENTITY version "20010611".
|
---|
19 |
|
---|
20 | 3) Find <ENTITY releasedate "Month, day, year"> and make sure it contains
|
---|
21 | the same date as the 'version' entity. If today is June 11th, 2001, change
|
---|
22 | it to: <!ENTITY releasedate "June 11th, 2001">
|
---|
23 |
|
---|
24 |
|
---|
25 |
|
---|
26 | * Adding a new package update to Bugzilla
|
---|
27 |
|
---|
28 | 1) Login to bugzilla
|
---|
29 |
|
---|
30 | 2) Open bug #30
|
---|
31 |
|
---|
32 | 3) Check if the package is listed from a previous update
|
---|
33 |
|
---|
34 | 4) If so, reopen it and change the version number to match the new one
|
---|
35 |
|
---|
36 | 5) If not, add a new bug and fill it out as usual
|
---|
37 |
|
---|
38 | 6) When added, go back to the new bug and under "Bug xx depends on"
|
---|
39 | enter "30" so that this new bug is added to the parent bug #30
|
---|
40 |
|
---|
41 | 7) Click on "Commit" to commit this change
|
---|
42 |
|
---|
43 |
|
---|
Note:
See
TracBrowser
for help on using the repository browser.