I've just recently spent the time going through the code on the site. I've finally got the whole thing figured out, and have been able to start pitching in a bit, but I have to say the learning process was a nightmare. It got me thinking. Since
PCX is going module based anyway has there been any thought or discussion to creating a repository with a powershell interface? I'm talking about something like CPAN/ppm that Perl has. If we create the base modules for interfacing with the repository,
and then define ways for submitting packages to the repository that would allow for dependencies we could modularize the Extensions, and allow for other developers to more easily add packages to PCX. It would allow users to pick and choose what they
want out of PCX, and it would mean that any module could be added to PCX.
My thoughts are to have commands like the following:
get-repository with query or filter properties to find packages that you are looking for... i.e. get-repository -filter mp3 to find all packages related to mp3s.
get-repositoryhelp to read a get-help on a cmdlet within a module before installing
import-repositorymodule package name - Would install a module and all dependant modules. It should also warn that it will be installing the additional modules. It should optionally not add the import-module command to the user's $profile.
remove-repositorymodule package name - To completely uninstall the module
Obviously there are some big things that need to be figured out.... hosting... database... controlling submissions/changes...
Any thoughts or interest?