661
edits
(Add to the "Development" category) |
Carandraug (talk | contribs) (→Rationale: what a package manager must be able to do) |
||
Line 25: | Line 25: | ||
See the user cases section below for several examples. | See the user cases section below for several examples. | ||
The definition of a package manager according to wikipedia: | |||
* Verifying file checksums to ensure correct and complete packages; | |||
* Verifying digital signatures to authenticate the origin of packages; | |||
* Applying file archivers to manage encapsulated files; | |||
* Upgrading software with latest versions, typically from a software repository; | |||
* Grouping of packages by function to reduce user confusion; | |||
* Managing dependencies to ensure a package is installed with all packages it requires. This resolved the problem known as Dependency Hell. | |||
== Available vs Loaded == | == Available vs Loaded == |