blob: 0d20667c68bb9497898b8cef785a2f2c61550526 (
plain)
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
|
<?xml version="1.0"?>
<guide self="ebuild-maintenance/package-moves/">
<chapter>
<title>Package and Slot Moves</title>
<body>
<p>
This chapter describes the use of package and slot moves.
</p>
</body>
<section>
<title>Moving a package</title>
<body>
<p>
Moving a package in the tree requires several operations. Firstly,
the package directory needs to be moved to the correct category
using <c>git mv</c>. After this, a new entry needs to be added to
the latest file in <c>profiles/updates/</c> in the
following format:
</p>
<pre>
move old-category/package-name new-category/package-name
</pre>
<p>
Following the update entry, ebuilds that have a
<uri link="::general-concepts/dependencies">dependency</uri>
to this package (in other words, the reverse dependencies of
the package to be moved) need to be updated properly.
</p>
<p>
Next is checking the files under <c>profiles/</c> such as
<c>profiles/package.mask</c> and update them to reflect the ebuild
move. Various eclasses automatically provide some of the dependencies upon
inherit, so the files under <c>eclass/</c> should be checked and updated
properly. If the package metadata.xml has tags with <c>restrict</c>
attribute, they should be updated to reflect the move. The
metadata.xml for various packages may contain references to the
package being moved using the <c><pkg></c> tag which need to be
updated accordingly as well. Lastly, the titles of the open bugs
related to the package should be updated.
</p>
<p>
Here is an example where the package
<c>net-misc/fwbuilder</c> is transparently moved to
<c>net-firewall/fwbuilder</c>:
</p>
<ol>
<li>Issue <c>git mv net-misc/fwbuilder net-firewall/fwbuilder</c></li>
<li>
<p>
Add the following entry to the latest file in
<c>profile/updates/</c>:
</p>
<p><c>move net-misc/fwbuilder net-firewall/fwbuilder</c></p>
</li>
<li>Update the reverse dependencies of the package</li>
<li>
Update <c>profiles/package.mask</c> and other related files under
<c>profiles/</c>
</li>
<li>Check the eclasses that may be referencing the package</li>
<li>
Update all the
<uri link="::ebuild-writing/misc-files/metadata">metadata.xml</uri>
files which contain a reference to this package using the
<c><pkg></c> tag or the <c>restrict</c> attribute.
</li>
<li>
Stage all the changed files using <c>git add</c>. For example: <c>git add
profiles/package.mask</c>
</li>
<li>
Commit all the changes in one commit using: <c>git commit --gpg-sign --signoff</c>
</li>
<li>
Update any <uri link="::general-concepts/news">news items</uri>
referencing the package in a <c>Display-If-Installed</c> header
or in the item's body (and increment their <c>Revision</c>).
</li>
<li>Update any open bugs related to the package</li>
</ol>
<p>
It is very important to commit all the changes in a single commit to ensure
that no breakage occurs. The commit message should follow a format similar
to the following:
</p>
<pre>
commit 7a699bcdce5c1412c02a2aa7717a31bc17c49058
Author: Miroslav Šulc <fordfrog@gentoo.org>
Date: Wed Dec 18 19:56:03 2019 +0100
media-libs/libclxclient: moved to x11-libs/libclxclient
Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org>
</pre>
</body>
</section>
<section>
<title>Changing ebuild's SLOT</title>
<body>
<p>
The process for changing the ebuild's SLOT is very similar to the
previous process. Besides changing the SLOT in the ebuild file, you
also need to create a new entry in <c>profiles/updates/</c> in
the Gentoo repository in the following format:
</p>
<pre>
slotmove app-text/gtkspell 0 2
</pre>
<p>
Make sure that you have fixed all the reverse dependencies and that
you have updated every file in <c>profiles/</c> directory that
happens to contain an entry which may be affected by your change.
</p>
</body>
</section>
</chapter>
</guide>
|
GitWeb