📄 doc068.htm
字号:
<html><body><a href="doc069.html"><img src=../icons/next.gif alt="Next"></a><a href="doc000.html"><img src=../icons/up.gif alt="Up"></a><a href="doc067.html"><img src=../icons/previous.gif alt="Previous"></a><a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a><a href="doc123.html"><img src=../icons/index.gif alt="Index"></a><hr><h2><a name="s9.4">9.4 Package Manipulation</a></h2><title>Package Manipulation</title><p><h3><a name="s9.4.1">9.4.1 Querying Packages</a></h3><title>Querying Packages</title><p>The easiest way to query a single package or group is to use the queryoption from the icon's context sensitive menu. If you want to querya more diverse set of packages, select them all and use the <tt>Query</tt>button in one of the windows.<p>Using either of these methods creates a window like the one shown in figure <a href="doc068.html#f46">46</a>. If you choose only one package, it will look a bit different however, so some of this won't apply.<p><p><a name="f46"></a><center><img src="img041.gif"></center><p><center>Figure 46:Query Window</center><p><p>On the very left of the window is a list of the packages that have beenqueried. Selecting one of them will change the information in therest of the window. You may step through them in order by using the<tt>Next</tt> and <tt>Previous</tt> buttons on the right side of the window.<p>The name, version, and release of the current package are in the topmiddle of the query window. Immediately below this is the descriptionof the package, which can be quite large. A scroll bar is thereto let you read the whole thing.<p>Below the description is a list of the files contained in the package.Along with the full path to the file, the file list tells you a coupleof other things. If a <tt>D</tt> appears to the left of the path, thatfile is a documentation file and would be a good thing to read. If a <tt>C</tt> appears there, then the file is a configuration file. A <tt>*</tt>means that the correct version of that file is not installed on yoursystem. This can occur because a more recent version of a packagewas installed or because two packages contain different versions of the same file.<p><p><a name="f47"></a><center><img src="img042.gif"></center><p><center>Figure 47:Query Details</center><p><p>More information on a package can be seen by clicking on the <tt>Details</tt>pushbutton. A window like the one in figure <a href="doc068.html#f47">47</a> will then appear. This lists more information about the package being displayed in the main query window. When you select a new package in the querywindow, the information in the details window will change to reflect your new choice.<p>You may also select, unselect, or verify a package while querying it by usingthe buttons provided. Click on the <tt>Close</tt> button whenyou are finished looking at the packages.<p><h3><a name="s9.4.2">9.4.2 Verifying Packages</a></h3><title>Verifying Packages</title><p>Verifying a package checks all of the files in the package toinsure they match the ones present on your system. The checksum, file size,permissions, and owner attributes are all checked against the database. This check can be used when you suspect that one of programs files hasbecome corrupted due to the installation of new programs.<p>Choosing the packages to verify is the same as choosing the packages toquery. Select the packages and use the <tt>Verify</tt> button or choose the <tt>Verify</tt> entry from a context sensitive menu. A window openslike the one in figure <a href="doc068.html#f48">48</a>.<p><p><a name="f48"></a><center><img src="img043.gif"></center><p><center>Figure 48:Verify Window</center><p><p>The three columns in this window describe the package with a problem init, the file that has the problem, and a brief description of thediscrepancies that were found. While the check is running, the currentfile being checked appears as the last element in the list, and theproblem is listed as <tt>(checking)</tt>. A full list of the problemsthat can be found through verification appears in figure <a href="doc068.html#f49">49</a>.<p><p><a name="f49"></a><center><table border><tr valign=top><td colspan=1 align=left nowrap><b>Problem</b></td><td colspan=1 align=left nowrap><b>Description</b> </td></tr><tr valign=top><td colspan=1 align=left nowrap> missing</td><td colspan=1 align=left nowrap>The file is no longer on your system </td></tr><tr valign=top><td colspan=1 align=left nowrap>mode</td><td colspan=1 align=left nowrap>permission bits have changed </td></tr><tr valign=top><td colspan=1 align=left nowrap>size</td><td colspan=1 align=left nowrap>file's size has changed </td></tr><tr valign=top><td colspan=1 align=left nowrap>uid</td><td colspan=1 align=left nowrap>owner's uid has changed </td></tr><tr valign=top><td colspan=1 align=left nowrap>gid</td><td colspan=1 align=left nowrap>owner's gid has changed </td></tr><tr valign=top><td colspan=1 align=left nowrap>md5</td><td colspan=1 align=left nowrap>the md5 checksum has changed </td></tr><tr valign=top><td colspan=1 align=left nowrap>link</td><td colspan=1 align=left nowrap>the file is a symlink to the wrong place</td></tr></table><p><center>Figure 49:Possible Problems found by Verification</center></center><p><p>To get more information on the problems found with a file, doubleclick on the file's path. A window like the one shown in figure <a href="doc068.html#f50">50</a>lists the expected and current values of the attributes that are amiss.<p><p><a name="f50"></a><center><img src="img044.gif"></center><p><center>Figure 50:Verification Details</center><p><p><h3><a name="s9.4.3">9.4.3 Installing New Packages</a></h3><title>Installing New Packages</title><p>Installing new packages from glint is very simple. First look at thepackages available for installation (see the section<a href="doc066.html#s9.2.3">9.2.3</a> for how to do this). You may select anynumber of these (and query them if you're not sure what they are) forinstallation (in the same manner you select packages for verification.) Ifyou want to install a single package or group, the context sensitivemenus provide a shortcut for doing so. Figure <a href="doc068.html#f51">51</a> shows a window with some packages selected for installation.<p><p><a name="f51"></a><center><img src="img045.gif"></center><p><center>Figure 51:Packages Selected for Installation</center><p><p>After you've begun the installation, a window appears like the one in figure <a href="doc068.html#f52">52</a>. It tracks the progress of the installation so you'll know something is happening. The top bar shows how much of the current package (whose name is listed inside of it) has been installed while the bottom graph shows how much of the total installation hasbeen finished. The number of packages, package sizes, and time estimatesare continually updated.<p><p><a name="f52"></a><center><img src="img046.gif"></center><p><center>Figure 52:Installation Progress</center><p><p>If a problem occurs during the installation, a window will appear listingany errors that occurred. If this happens, you should correct the problemsand then try again. <p>After the installation has completed, the package and groups thathave been installed are moved from the available window to the mainglint window to show you that they have been successfully installed.<p><h4><a name="s9.4.3.1">9.4.3.1 Upgrading Packages</a></h4><title>Upgrading Packages</title><p>When a new version of a package has been released, it is easy to install iton your system. Select the packages from the window of available packagesin the same way you select packages for installation. Both the<tt>Upgrade</tt> button and the context sensitive menus will begin theupgrade.<p>During the upgrade, you'll see a progress indicator like the one forinstalling packages. When it's finished, the installed packages willappear in the the main glint windows and any old versions of the packageswill be removed.<p>It is much better to use the upgrade option than to uninstall the oldversions of a package and then install the new one. Using upgradeensures that any changes you made to package configuration filesget preserved properly, while doing it manually could cause thosechanges to be lost.<p>If you run out of disk space during an installation, the install will fail.However, the package which was being installed when the error occurredmay leave some files around. To clean this up, reinstall the packageafter you've made more disk space available.<p><h3><a name="s9.4.4">9.4.4 Uninstalling Packages</a></h3><title>Uninstalling Packages</title><p>Uninstalling a package is not the same as upgrading one. When a packageis uninstalled, any files it uses that are not needed by other packageson your system are removed. Changed configuration files are copied to <tt><filename>.rpmsave</tt> so you can reuse them later. <p>Like verifying and querying packages, you can remove a package throughthe buttons on the right of the glint window or through a context sensitivemenu. Remember that when you make a choice from a group's menu, theoperation is performed on all of the packages in that group, so becareful!<p><p><a name="f53"></a><center><img src="img047.gif"></center><p><center>Figure 53:Uninstall Window</center><p><p>Once you've begun the uninstall, glint asks for confirmation,showing a window like the one in figure <a href="doc068.html#f53">53</a>. All of the packages that are aboutto be uninstalled are listed. You should look at them all to ensure you'renot about to remove something you want to keep. Clicking the <tt>Yes</tt> buttonwill start the uninstallation process. After it completes, the packages andgroups that have been removed will disappear from any windows they were in.<p><p><hr><a href="doc069.html"><img src=../icons/next.gif alt="Next"></a><a href="doc000.html"><img src=../icons/up.gif alt="Up"></a><a href="doc067.html"><img src=../icons/previous.gif alt="Previous"></a><a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a><a href="doc123.html"><img src=../icons/index.gif alt="Index"></a><hr></body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -