1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
12 >Using Templates</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos User Guide"
20 HREF="ecos-user-guide.html"><LINK
22 TITLE="Updating the Configuration"
23 HREF="config-tool-updating-configuration.html"><LINK
25 TITLE="Platform Selection"
26 HREF="config-tool-platform-selection.html"><LINK
29 HREF="config-tool-searching.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="config-tool-platform-selection.html"
65 >Chapter 19. Updating the Configuration</TD
71 HREF="config-tool-searching.html"
85 NAME="CONFIG-TOOL-USING-TEMPLATES">Using Templates</H1
87 >To load a configuration based on a template, select
102 >The following dialog box will be displayed:</P
108 >Figure 19-4. Templates dialog box</B
112 SRC="pix/templates.png"></P
115 >Change the hardware template, the packages template, or
116 both. To select a hardware template, choose from the first
117 drop-list. To choose a packages template, choose from the
118 second. Brief descriptions of each kind of template are
119 provided in the corresponding edit boxes.</P
125 NAME="RESOLVING-CONFLICTS">Resolving conflicts</H2
127 >During the process of configuring <SPAN
131 that conflicts will be created. For more details of the
132 meaning of conflicts, see <A
133 HREF="cdl-concepts.html"
137 >The Conflicts Window displays all conflicts in the
138 current configuration. Additionally, a window in the
139 status bar displays a count of the conflicts. Because the
140 resolution of conflicts can be time-consuming, a mechanism
141 exists whereby conflicts can be resolved
144 >You can choose to have a conflicts resolution dialog
145 box displayed by means of the <SPAN
149 >View->Settings...
152 >menu item, on the <SPAN
156 >Conflict Resolution</I
159 tab of the dialog.</P
165 >Figure 19-5. Options</B
169 SRC="pix/ToolsOptions.png"></P
172 >You can choose to have conflicts checked under the
173 following circumstances:</P
179 >After any item is changed (in other words,
180 as soon as the conflict is created)</P
184 >Before saving the configuration (including
193 >The method you chose depends on how much you need
194 your configuration to be free of conflicts. You may
195 want to avoid having to clean up all the conflicts at
196 once, or you may want to keep the configuration
197 consistent at all times. If you have major changes to
198 implement, which may resolve the conflicts, then you
199 might want to wait until after you have completed
200 these changes before you check for conflicts.</P
208 >If you choose to check conflicts after any item
209 is changed, only newly arising conflicts are displayed.
210 If you choose to check for conflicts before saving the
211 configuration, the complete set is
221 NAME="AEN1444">Automatic resolution</H2
223 >If you check the “Automatically suggest
224 fixes” check box, a conflicts resolution dialog box
225 will be displayed whenever new conflicts are created. The
226 same dialog box may be displayed at any stage by means of
231 >Tools->Resolve Conflicts</I
243 >The conflicts resolution dialog box contains two major windows. </P
249 >Figure 19-6. Resolve conflicts window</B
253 SRC="pix/Conflicts.png"></P
256 >The upper contains the set of conflicts to be addressed; the
257 format of the data being as that of the Conflicts Window. The lower
258 window contains a set of proposed resolutions – each entry
259 is a suggested configuration item value change that as a whole may
260 be expected to lead to the currently selected conflict being resolved. </P
262 >Note that there is no guarantee:</P
268 >that automatic resolutions will be determinable for every
273 > that the resolutions for separate conflicts will be independent.
274 In other words, the resolution of one conflict may serve to prevent
275 the resolution of another.</P
279 > that the resolution conflicts will not create further
284 >The above warnings are, however, conservative. In practice
285 (so long as the number and extent of conflicts are limited) automatic
286 conflict resolution may be used to good effect to correct problems
287 without undue amounts of programmer intervention.</P
289 >In order to select the conflicts to be applied, select or
290 clear the check boxes against the resolutions for each proposed
291 resolution. By default all resolutions are selected; you can return
292 to the default state (in other words, cause all check boxes for
293 each conflict to again become checked) by pressing the “Reset” button.
294 Note that multiple selection may be used in the resolutions control
295 to allow ranges of check boxes to be toggled in one gesture.</P
297 >When you are happy to apply the selected resolutions for each
298 conflict displayed, click <SPAN
305 apply the resolutions. Alternatively you may cancel from the dialog
306 box without any resolutions being applied.</P
314 SUMMARY="Footer navigation table"
325 HREF="config-tool-platform-selection.html"
334 HREF="ecos-user-guide.html"
343 HREF="config-tool-searching.html"
353 >Platform Selection</TD
359 HREF="config-tool-updating-configuration.html"