<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#330033">
New package manager from M$... article <a
href="http://www.neowin.net/news/windows-10-oneget-a-linux-style-package-management-framework">here</a>.<br>
<br>
It seems doubtful that M$ will eliminate .msi (their obscure, hard
to configure and use, installation format), so it seems doubtful
that the addition of OneGet will _force_ any changes to Python
packaging.<br>
<br>
However, it does open the question in my mind about whether there
will be any _benefits_ of OneGet that would inspire helpful, useful
changes to Python packaging. They speak of "trusted repositories",
and the like, and it sounds like a the various *nix package managers
(apt-get, et alia), but perhaps allowing multiple repositories
rather than just a single source vendor repository (I'm actually not
sure if *nix package managers allow multiple repositories or not,
but from the way people talk about them, it always sounds like a
"distribution" also provides "a repository" of additional packages).<br>
<br>
"trusted repositories" sounds more like Perl's CPAN.<br>
<br>
<a
href="http://blogs.technet.com/b/windowsserver/archive/2014/04/03/windows-management-framework-v5-preview.aspx">One
of the links</a> contains this quote: "This first version of
OneGet installs and searches software from Chocolatey repositories.
Support of additional repositories will come in subsequent
versions."<br>
<br>
I have no clue what a Chocolatey repository is (yet, will Google),
but unknown others will come, it says... whether it is possible to
write a "repository plugin" such that Perl's CPAN or Python's PyPI
or other preexisting repositories can be accessed is not clear.<br>
<br>
The relationship between PowerShell and OneGet is not clear
either... is OneGet written in PowerShell, or is PowerShell just one
way to invoke OneGet, or???<br>
<br>
Just a heads up.<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>