Provide means to qualify Script names to avoid conflicts
The PowerShell Gallery currently qualifies 'Scripts' by name only. For example, if someone has already published Some-Script, I have no way to publish my own Some-Script, even if the original is related only in name, has major functional differences, etc.
It would be helpful to allow qualifying these. Perhaps resolve by date published first (i.e. compatible with current system), while allowing qualification by username, similar to how GitHub handles this.
Thus, I could install RamblingCookieMonster\Some-Script, even if EvilDoer\Some-Script already existed.
The same design could also be extended to modules, although those seem less likely to conflict (this may change if the open source community adopts PowerShell and starts publishing more modules, so... might be worth looking at...)
Tim Curwick commented
I would prefer something as consistent as possible to namespaces in functionality, terminology, and syntax. All existing scripts and modules would be in a default namespace.
Warren F. commented
I'm not tied to any implementation, but to address Joel's comment, my original thought was as follows:
* UserA publishes GenericModuleName
* UserB can't publish GenericModuleName
* Install-Module install's UserA's GenericModuleName
* UserA publishes GenericModuleName (first)
* UserB publishes GenericModuleName (second)
* Install-Module GenericModuleName installs UserA's module due to publication date
* Install-Module UserB/GenericModuleName (or, Install-Module GenericModuleName -Author UserB) installs UserB's module
If I need both modules on a machine, I can still Save-Module or use different scopes, or, at some point ideally, virtual environments...
Joel "Jaykul" Bennett commented
Personally, I think it would be a bad idea (and a breaking change) for modules, but a great idea for scripts.
Rob Nelson commented
I'm partial to author/name.