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 >Managing the Package Repository</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="Configuration and the Package Repository"
23 HREF="configuration-and-the-package-repository.html"><LINK
25 TITLE="Modifying the Memory Layout"
26 HREF="modifying-the-memory-layout.html"><LINK
28 TITLE="Package Structure"
29 HREF="package-structure.html"></HEAD
40 SUMMARY="Header navigation table"
57 HREF="modifying-the-memory-layout.html"
71 HREF="package-structure.html"
84 NAME="MANAGING-PACKAGE-REPOSITORY">Chapter 29. Managing the Package Repository</H1
94 HREF="managing-package-repository.html#PACKAGE-INSTALLATION"
95 >Package Installation</A
99 HREF="package-structure.html"
100 >Package Structure</A
105 >A source distribution of <SPAN
108 > consists of a number of
109 packages, such as the kernel, the C library, and the
110 µITRON subsystems. These are
111 individually versioned in the tree structure of the source
112 code, to support distribution on a per-package basis and to
113 support third party packages whose versioning systems might be
120 Administration Tool</SPAN
121 > is used to manage the
122 installation and removal of packages from a variety of sources
123 with potentially multiple versions.</P
125 >The presence of the version information in the source tree
126 structure might be a hindrance to the use of a separate source
127 control system such as <SPAN
141 in this way, you can rename all the version components to some
142 common name (such as “current”) thus unifying the
143 structure of source trees from distinct <SPAN
151 > build system will treat any such name as just another
152 version of the package(s), and support building in exactly the same
153 way. However, performing this rename invalidates any existing build
154 trees that referred to the versioned source tree, so do the rename
155 first, before any other work, and do a complete rebuild afterwards.</P
161 NAME="PACKAGE-INSTALLATION">Package Installation</H1
163 >Package installation and removal is performed using the
169 >Package Administration Tool</SPAN
171 tool is a Tcl script named
176 the user to add new <SPAN
179 > packages and new versions of
180 existing packages to an <SPAN
183 > repository. Such packages must
184 be distributed as a single file in the <SPAN
188 distribution format. Unwanted packages may also be removed
189 from the repository using this tool. A graphical version of
190 the tool is provided as part of the
196 >Configuration Tool</SPAN
203 NAME="AEN3071">Using the Administration Tool</H2
212 Administration Tool</SPAN
213 >, provided as part of the
221 >, provides functions equivalent to the command-line
222 version for those who prefer a Windows-based interface.</P
224 >It may be invoked in one of two ways:</P
236 >Start->Programs->
237 eCos->Package Administration
253 >Tools->Administration</SPAN
261 SRC="pix/admin.png"></P
264 >The main window of the tool displays the packages which are
265 currently installed in the form of a tree. The installed versions
266 of each package may be examined by expanding the tree.</P
268 >Packages may be added to the <SPAN
271 > repository by clicking on
281 > package distribution
282 file to be added is then selected via a <SPAN
291 >Packages may be removed by selecting a package in the tree
292 and then clicking on the <SPAN
299 a package node is selected, all versions of the selected package
300 will be removed. If a package version node is selected, only the
301 selected version of the package will be removed.</P
308 NAME="AEN3099">Using the command line</H2
314 script is located in the base of the <SPAN
318 a command of the following form under versions of
328 >$ tclsh ecosadmin.tcl <command></PRE
333 >Under Windows, a command of the following form may be used
334 at the Cygwin command line prompt:</P
343 >$ cygtclsh80 ecosadmin.tcl <command></PRE
348 >The following commands are available:</P
361 >Adds the packages contained with the specified package distribution
365 > repository and updates the package database accordingly.
369 > package distribution files are given the <TT
377 >remove <package> [ --version=<version> ]</B
381 >Removes the specified package from the <SPAN
385 repository and updates the package database
386 accordingly. Where the optional version qualifier is
387 used, only the specified version of the package is
397 >Produces a list of the packages which
398 are currently installed and their versions. The
399 available templates and hardware targets are also
405 >Note that is is possible to remove critical packages
406 such as the common HAL package using this tool. Users
407 should take care to avoid such errors since core <SPAN
411 packages may only be re-installed in the context of a
412 complete re-installation of <SPAN
424 SUMMARY="Footer navigation table"
435 HREF="modifying-the-memory-layout.html"
444 HREF="ecos-user-guide.html"
453 HREF="package-structure.html"
463 >Modifying the Memory Layout</TD
469 HREF="configuration-and-the-package-repository.html"
477 >Package Structure</TD