I'm really excited to release the new version, but the feature parity needs to be there first.
The early designs of Chocolatey were somewhat dependent on NuGet.exe which doesn't have all of the same functionality that has as far as package management (although it's got some really obtuse bugs that I've filed while writing the C# version of choco).
#Choco vlc media player install
There are some packages right now where you do install multiple versions (Ruby and Python), but they are few and far between. Rest assured this is not how the new version works. I've been talking about rewriting it since the end of the first year. FWIW, the PowerShell version of Chocolatey was an experiment that has stuck around for too long. Chocolatey folders can get really crazy with updates over time with the PowerShell version. UPDATE: In choco 0.9.9+ (C# compiled version) this is no longer the case. Until then I don't see any added value in Chocolatey. It seems that it should be addressed in a new client written in C# instead of PowerShell, but it wasn't released yet (should be released before the end of 2014).
It's also discussed for example here and here, but nothing has changed during a year. Who needs to use different versions of Git, Atom, VLC media player, Chrome, etc. Each one of these two approaches is good for different purpose. There is a quite big difference between a package managers (like Chocolatey, apt-get or brew) and a dependency managers (like npm or bower). It advertises itself as " apt-get for Windows" and apt-get is a package manager. I would say that Chocolatey works more as a dependency manager, but it should be a package manager.
#Choco vlc media player software
Actually I wish I'm missing something 🙂 Because software management on Windows is quite a pain for years. I don't think this is suitable for real usage. What if I don't have installed just one package using Chocolatey, but tens of packages?Īlso the fact that each version of package is in individual directory causes various issues (like for example this, this or this). Should I just manually remove older versions of packages and hope there are no dependencies outside of Chocolatey's package directory? Therefore I wonder what's the proper way of managing package versions using Chocolatey. And there is also currently no way to uninstall previously installed packages using Chocolatey except of the most recent one.
#Choco vlc media player update
Chocolatey in fact doesn't update a package it just installs a new version besides an older one, and it doesn't matter if you use a command choco update or choco update all. Then I noticed that I have all previously installed versions of Atom still present in a Chocolatey's lib directory. New versions of Atom are released pretty frequently, so I have updated this package several times. I'm concerned the most about proper way of package updating.įor example, I have installed Atom editor using Chocolatey. At the beginning I was excited, but after some time I'm not sure if it's usable yet. I have been using Chocolatey for some time. Later versions are completely rewritten from PowerShell scripts to a C# application and whole process of package management was improved a lot. NOTE: This question was valid for Chocolatey 0.9.8 and bellow.
0 kommentar(er)
