summaryrefslogtreecommitdiffstats
path: root/build_tools/larch7/larch0/docs/html/gui_installation.html
blob: b6894352faf80899b7d3e5b51ab81095d726a775 (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
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<html>
<head>
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
<title>GUI Tab: Installation</title>
<!-- (en) Add your meta data here -->

<link href="css/larchdocs.css" rel="stylesheet" type="text/css"/>
<!--[if lte IE 7]>
<link href="css/yaml/core/iehacks.css" rel="stylesheet" type="text/css" />
<![endif]-->
</head>

<body>
<!-- skip link navigation -->
<ul id="skiplinks">
    <li><a class="skip" href="#col1">Skip to main content (Press Enter).</a></li>
</ul>

<div class="page_margins">
  <div class="page">
    <div id="top"><div id="tm"></div></div>
     <!-- begin: #col1 -->
      <div id="col1" role="main">
        <div id="col1_content">
          <div id="header" role="banner">
            <h1><span><em>live Arch Linux</em> builder</span></h1>
          </div>

      <!-- begin: #col3 navigation column -->
      <div id="col3" role="complementary">
        <div id="col3_content">
          <img class="indent2" alt="larch logo" src="css/screen/larch150x.png" width="150" height="150" />
              <div class="vlist">
                <ul>
                  <li><a href="index.html"><h6>Table Of Contents</h6></a></li>
                  <li><a href="gui_larchify.html"><h6>Next:</h6>
                    <div class="indent1">GUI Tab: Larchify</div></a></li>
                  <li><a href="gui_project_settings.html"><h6>Previous:</h6>
                    <div class="indent1">GUI Tab: Project Settings</div></a></li>
                </ul>
              </div>
        </div>
      </div>
      <!-- end: #col3 -->

<div class="larchdocs">

<h2 id="pagetitle" level="2">GUI Tab: Installation</h2>

<p>This tab mixes profile options and project options. Which packages
to install is a feature of the profile, as is the basic design of the
'pacman.conf' file. The exact location of the packages (repository
and cache paths) are more related to the build environment.
</p>

<h3>Package selection</h3>

<p>See <a href="archin.html#package_selection">here</a> for details of how
the list of packages to be installed is built up. The gui offers
convenient editing of the 'addedpacks' and 'vetopacks' files.
</p>

<p><em>pacman</em> configuration is handled in separate parts.
'pacman.conf' is effectively split into two, the options part and the
repositories part can be edited separately, though the default options
should be alright for most purposes. This split might ease management
of updates to the structure of the file 'pacman.conf' with new pacman
releases. Default versions of both parts (for the options part a complete
pacman.conf can be used, the repositories will be stripped automatically)
are supplied in the 'data' directory of the 'larch' package.
A simplified format is used for the repository file, details can be
found <a href="archin.html#pacman_conf">here</a>.
</p>

<p>Note that the <em>larch</em> repository must be available for building
the <em>live</em> system, i.e. it must be included in the 'pacman.conf'
used for the installation process. It is not strictly necessary for the
resulting <em>live</em> system to include this repository. See below for
further details.
</p>

<h3>'mirrorlist'</h3>

<p>It is possible to customize the 'mirrorlist' file used for installation.
This can be very convenient, because when building a <em>live</em> system
the build environment can be very different from the run-time environment.
For example, you might use local package repositories for building which
cannot possibly be available when the <em>live</em> system is used.
</p>

<p>Customized versions of the 'mirrorlist' file are not regarded as
belonging to the profile, because they are build environment specific, so
they are stored in the project directory, which is made current when the
larch backend scripts are run.
</p>

<h3>Special installation repositories and cache</h3>

<p>Adjustments to the installation repository file and cache location are
treated as 'advanced' options, because in many cases the defaults will be
perfectly adequate.
</p>

<h4>Using different mirrors/repositories for the installation</h4>

<p>The second part of the 'pacman.conf' file, the repository list, can be
specified separately for the installation, via the frame
'Use project repository list'. For certain build environments this can be
very useful.
</p>

<p>A further way of getting a distinct 'pacman.conf' in the resulting
<em>live</em> system is to put it in the profile's 'rootoverlay' directory
(in the '/etc' subdirectory, as usual).
</p>

<h4>Package cache</h4>

<p>Normally the host's standard package cache will be used for the
installation, but it is possible to use a non-standard location. I guess,
however, that this will not normally be necessary.
</p>

<h3>GUI Tab: Installation Tweaks</h3>

<p>At present the only thing offered here is a bit of assistance in
managing packages within the installation. The database can be
resynchronized, packages can be added or removed. During testing it can
be helpful to be able to make quick changes like this, but it is probably
not a good idea to use these facilities too freely. The installation will
differ from the specification in the profile (unless you immediately edit
the profile too), which may be no problem for one-offs, but if you ever
want to reuse the profile you may well lose track of what changes you have
made.
</p>

</div>



          <div class="topref"><a href="#top">Top</a></div>
        </div>
    <!-- begin: #footer -->
    <div id="footer">
      <div id="footer-content" role="contentinfo">© 2010 Michael Towers<br />
        Page layout assisted by <a href="http://www.yaml.de/">YAML</a> and
        <a href="http://www.kuwata-lab.com/tenjin/">pyTenjin</a>
      </div>
    </div>
    <!-- end: #footer -->
      </div>
      <!-- end: #col1 -->
    <div id="bottom"><div id="bl"><div id="bm"></div></div></div>
  </div>
</div>
<!-- full skiplink functionality in webkit browsers -->
<script src="css/yaml/core/js/webkit-focusfix.js" type="text/javascript"></script>
</body>
</html>