blob: 9625a1a53c4df14e958a2a6bbf1b728f3630d656 (
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
|
<?xml version="1.0"?>
<guide self="general-concepts/slotting/">
<chapter>
<title>Slotting</title>
<body>
<p>
Packages can support having multiple versions installed simultaneously. This is
useful for libraries which may have changed interfaces between versions <d/> for
example, the <c>gtk+</c> package can install both versions <c>1.2</c> and <c>2.6</c> in
parallel. This feature is called slotting.
</p>
<p>
Most packages have no need for slotting. These packages specify <c>SLOT="0"</c> in
the ebuilds. This is <b>not</b> the same as specifying an empty slot <d/> an empty
slot means "disable slotting entirely", and should not be used.
</p>
<p>
Portage permits at most one instance of a package installation <e>per <c>SLOT</c>
value</e>. For example, say we have the following:
</p>
<ul>
<li><c>foo-1.1</c> with <c>SLOT="1"</c></li>
<li><c>foo-1.2</c> with <c>SLOT="1"</c></li>
<li><c>foo-2.0</c> with <c>SLOT="2"</c></li>
<li><c>foo-2.1</c> with <c>SLOT="2"</c></li>
</ul>
<p>
Then the user could have, say, <c>foo-1.2</c> and <c>foo-2.0</c> installed in
parallel, but <e>not</e> <c>foo-1.1</c> and <c>foo-1.2</c>. Note that it is entirely
possible that the user may have <c>foo-2.0</c> installed and no <c>foo-1.x</c> at all.
</p>
<p>
It is not possible to <c>DEPEND</c> upon a package in a specific slot.
</p>
<p>
Currently portage will accept an arbitrary string for the value of <c>SLOT</c>. For
future compatibility, it is recommended that slots contain only characters which
are allowed in an ebuild name or version (alphanumerics, hypens, full stops,
underscores, the plus character) <d/> other characters may cause problems with
future portage enhancements.
</p>
</body>
</chapter>
</guide>
|
GitWeb
