windows - Proper using of Chocolatey (package update / version management) -

windows - Proper using of Chocolatey (package update / version management) -

note: question valid chocolatey 0.9.8 , bellow. later versions rewritten powershell scripts c# application , whole process of bundle management improved lot.

i have been using chocolatey time. @ origin excited, after time i'm not sure if it's usable yet. i'm concerned proper way of bundle updating.

i have installed illustration atom editor using chocolatey. new versions of atom released pretty frequently, have updated bundle several times. noticed have installed versions of atom still nowadays in chocolatey's lib directory. chocolatey in fact doesn't update package, installs new version besides older 1 , doesn't matter if utilize command choco update <package> or choco update all. , there no way uninstall installed packages using chocolatey except of recent one.

therefore wonder what's proper way of managing bundle versions using chocolatey. should manually remove older versions of packages , hope there no dependencies outside of chocolatey's bundle directory?

or rather this?

choco uninstall <package> choco install <package>

what if don't have installed 1 bundle using chocolatey, tens of packages?

also fact each version of bundle in individual directory causes various issues (like illustration this, this or this).

i don't think suitable real using. or maybe i'm missing something. wish i'm missing :) because software management on windows quite pain years. it's mess.

i chocolatey works more dependency manager, should package manager. advertises "apt-get windows" , apt-get bundle manager. there quite big difference between bundle managers (like chocolatey, apt-get or brew) , dependency managers (like npm or bower). each 1 of these 2 approaches different purpose. needs utilize different versions of git, atom, vlc, chrome etc. @ same time?

it's discussed illustration here , here, nil has changed during year. it seems should addressed in new client written in c# instead of powershell, wasn't released yet (should released before end of 2014). until don't see added value in chocolatey.

update: in choco 0.9.9+ (c# compiled version) no longer case.

you correct. chocolatey folders can crazy updates on time posh version. fwiw, posh version of chocolatey experiment has stuck around long. i've been talking rewriting since end of first year. agreed seeing ugly. rest assured not how new version works. there packages right install multiple versions (ruby/python) few , far between.

the designs of chocolatey dependent on nuget.exe doesn't have of same functionality nuget.core.dll has far bundle management (although it's got obtuse bugs i've filed while writing c# version of choco).

i'm excited release new version, feature parity needs there first. fossed either before release or @ same time. version going back upwards professional/business extensions. there no way effort current pos(h) version. ;)

right can manually jump lib folder , delete of older folders. older versions not considered there chocolatey in cases. it's looking @ latest versions. error making not deleting older folders (and using version on folder in first place).

windows nuget package-managers chocolatey package-management