Centralized Package Management for PowerShell - by deadlydog

Status : 


Sign in
to vote
ID 800050 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 9/9/2013 12:52:47 PM
Access Restriction Public


Centralized Package Management would be a huge win for PowerShell.  Modules are a great part of PowerShell, but writing scripts for other people/computers that depend on them can be problematic, as you can't guarantee that the modules will be installed on those computers.  If PowerShell had something similar to Ruby Gems that would be great, where at the top of the script you specify the modules that the script depends on, and if they aren't installed on the current PC already then they are automatically downloaded and installed.

This would encourage more people to write reusable modules, and would avoid people copy/pasting multiple files/modules into a single script file, or having to zip up the whole suite of scripts that a script depends on when distributing it to other people/computers.
Sign in to post a comment.
Posted by deadlydog on 11/16/2013 at 7:10 AM
Similar related suggestion at https://connect.microsoft.com/PowerShell/feedback/details/684680/powershell-module-finder-and-manager.
Posted by deadlydog on 9/12/2013 at 2:21 PM
I've blogged about this to try and get some suggestions from people about what they would like this to look like, or possible alternative solutions that can be used until this is implemented in PowerShell (hopefully v5). http://blog.danskingdom.com/powershell-needs-a-centralized-package-management-solution/