Oh, wow. Please, can I get a decent command line now?
you can get conemu
Introducing PackageManagement in Windows 10
31–40 of 221 posts
Re: Introducing PackageManagement in Windows 10
#32As someone who isn't very familiar with package managers, what does this mean for Chocolatey?
https://groups.google.com/forum/#!topic/chocolatey/a8WdEoF-M... > What does this mean for Chocolatey? More awesome. More security. More better. Chocolatey is going nowhere, OneGet is a core API that enables package managers to hook in and take advantage of Windows components easier. > The best understanding I have is that OneGet is shipping with a prototype plugin compatible with Chocolatey. Right now this means that…
So Chocolatey is gonna use OneGet in the back? I was thinking it would be a package provider for OneGet instead.
Re: Introducing PackageManagement in Windows 10
#33Please give us something that doesn't require PowerShell, since PowerShell never just works. Just look at the ridiculous bullshit that you have to deal with when you want to use Chocolatey (from the Chocolatey install guide): Note: You must have your execution policy set to unrestricted (or at least in bypass) for this to work (Set-ExecutionPolicy Unrestricted). There have been reports that RemoteSigned is enough for…
PowerShell is disabled by default for security reasons. It's one command to enable it.
Yeah, one command - on every machine... Meanwhile on Linux, I don't need to do any special configuration to run scripts.
Re: Introducing PackageManagement in Windows 10
#34Earlier quoted context omitted.
PowerShell is disabled by default for security reasons. It's one command to enable it.
Yeah, one command - on every machine... Meanwhile on Linux, I don't need to do any special configuration to run scripts.
> Yeah, one command - on every machine...
I think Microsoft envisions centrally-managed environments, rather than those with lots of Windows machines that aren't centrally managed.
Re: Introducing PackageManagement in Windows 10
#35Re: Introducing PackageManagement in Windows 10
#36Earlier quoted context omitted.
PowerShell is disabled by default for security reasons. It's one command to enable it.
Yeah, one command - on every machine... Meanwhile on Linux, I don't need to do any special configuration to run scripts.
You do if those scripts can affect the system and need to run as root. Powershell is incredibly powerful (and dangerous) and some security isn't the worst thing.
Re: Introducing PackageManagement in Windows 10
#37Earlier quoted context omitted.
PowerShell is disabled by default for security reasons. It's one command to enable it.
Yeah, one command - on every machine... Meanwhile on Linux, I don't need to do any special configuration to run scripts.
> on every machine...
Or through one group policy pushed to every machine.
Re: Introducing PackageManagement in Windows 10
#38I recently blogged about the Linux world needing something like this. http://leto.electropoiesis.org/propaganda/plugins-and-packag... I hate having to individually update my Wordpress install, my Rubies, my system packages, my IDE (be it Eclipse or Android Studio), a separate TeXLive install from the OS packages, even Vim now has its own package management with Pathogen... There must be some way to _unify_ this proli…
It's a disaster. The proper way to do it is distro packages, but for some reason every language, framework, ecosystem and individual developer wants to reinvent this particular wheel. I really don't understand why.
Re: Introducing PackageManagement in Windows 10
#39Earlier quoted context omitted.
Unify != replace. Guix/Nix don't integrate multiple package managers, it just is Another Package Manager.
They are the only package managers I know of capable of unifying package management with a single set of tools. Unifying multiple distinct package managers is a fool's errand.
> Unifying multiple distinct package managers is a fool's errand
I disagree. Why do you think that is the case?
Re: Introducing PackageManagement in Windows 10
#40Perhaps I missed it, but the article doesn't mention this in any way: Windows ABSOLUTELY needs a way to go from 'Fresh Install' to 'Fully upgraded' with minimal interaction. Linux can do this: run `apt-get dist-upgrade` in Ubuntu, and you get all of the most recent updates. However, in Windows, you install 3 updates, restart, install 5 updates, restart, install 110 updates, restart....
Yeah I think they need to address this but it's going to require a pretty big, fundamental change so it might take a while. It's certainly needed.