computing:windows_pkg_mgmt
Differences
This shows you the differences between two versions of the page.
Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
computing:windows_pkg_mgmt [2015/09/11 12:09] gcooper |
computing:windows_pkg_mgmt [2015/09/11 12:11] (current) gcooper |
http://blogs.technet.com/b/packagemanagement/archive/2015/05/05/10-things-about-oneget-that-are-completely-different-than-you-think.aspx | http://blogs.technet.com/b/packagemanagement/archive/2015/05/05/10-things-about-oneget-that-are-completely-different-than-you-think.aspx |
| |
PackageManagement is essentially a **Package Management Aggregator**. It creates a unified and consistent PowerShell interface for users and provides a plug-in model at the back end that different installer technologies or package managers can plug-in as providers, using PackageManagement APIs. Each provider further manages one or multiple package sources (repositories) where software packages are stored. | **Introduction**: http://blogs.technet.com/b/packagemanagement/archive/2015/04/29/introducing-packagemanagement-in-windows-10.aspx |
| |
* Providers = Package Managers | **From the Introduction**: PackageManagement is essentially a **Package Management Aggregator**. It creates a unified and consistent PowerShell interface for users and provides a plug-in model at the back end that different installer technologies or package managers can plug-in as providers, using PackageManagement APIs. Each provider further manages one or multiple package sources (repositories) where software packages are stored. |
| |
| * **Providers** = Package Managers |
* Like MSI | * Like MSI |
* Package Sources = Repositories | * **Package Sources** = Repositories |
| |
{{ :computing:packagemanagement-architecture.png?600 |PackageManagement Architecture}} | {{ :computing:packagemanagement-architecture.png?600 |PackageManagement Architecture}} |
computing/windows_pkg_mgmt.1441994959.txt.gz · Last modified: 2015/09/11 12:09 by gcooper