package_management
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
package_management [2018/08/30 20:04] 127.0.0.1 external edit |
package_management [2018/12/31 16:28] (current) z5t1 [Setting up Pickle] |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| ===== Setting up Pickle ===== | ===== Setting up Pickle ===== | ||
| - | Pickle (like most other update managers) stores a local cache of the package and update list. Before actually installing or updating packages, it is necessary to refresh this local cache (otherwise you could end up installing old packages). This is done by running 'pickle --update'. It is important to note that this should be done **routinely**. It is a good idea to update your cache every time before running Pickle. | + | Pickle (like most other update managers) stores a local cache of the package and update list. Before actually installing or updating packages, it is necessary to refresh this local cache (otherwise you could end up installing old packages). This is done by running ''%%pickle --update%%''. It is important to note that this should be done **routinely**. It is a good idea to update your cache before running Pickle every time. |
| ===== Updating the System ===== | ===== Updating the System ===== | ||
| - | To display a list of available updates, simply run 'pickle'. This will display an interactive list of updates for you to install. Simply select the packages you want to update and select 'Ok'. Pickle will then download and update the selected packages. | + | To display a list of available updates, simply run ''%%pickle --update && pickle%%''. This will display an interactive list of updates for you to install. Select the packages you want to update and select 'Ok'. Pickle will then download and update the selected packages. |
| - | It is important to note that a package's configuration files may be overwritten during the update process, so it's a good idea to back up any important configuration files (which are generally found in /etc) **before** updating a package. These files may or may not be preserved, depending on the package. A list of files belonging to a given package can be obtained using pkgtool by selecting "View" and then the package you wish to view the files for. | + | It is important to note that a package's configuration files may be overwritten during the update process, so it's a good idea to back up any important configuration files (which are generally found in /etc) **before** updating a package. These files may or may not be preserved, depending on the package. A list of files belonging to a given package can be obtained by running ''pkgtool'', selecting "View" and then selecting the package you wish to view the files for. |
| - | Any packages that are not selected for update can optionally be added to the ignore list. This will prevent Pickle from displaying these updates in the future. If you decide to install these updates in the future, it will first be necessary to reset this ignore list. This is done by running 'pickle --hard-update'. | + | Any packages that are not selected for update can optionally be added to the ignore list. This will prevent Pickle from displaying these updates in the future. If you decide to install these updates in the future, it will first be necessary to reset this ignore list. This is done by running ''%%pickle --hard-update%%''. |
| ==== A Note About Update Types ==== | ==== A Note About Update Types ==== | ||
package_management.1535659495.txt.gz ยท Last modified: 2018/08/30 20:04 by 127.0.0.1
Page Tools
