Closed devblackops closed 6 years ago
I'm also facing this issue which forces me to reinvent the wheel :(
Sooo... Can you think of any reason to parameterize this, or should we just force AllowClobber
when Install-Module is called?
IMHO it's not a very helpful parameter, particularly in this scenario. Might be easier to just hard code it? Or if we really need to parameterize it, default to using it?
Also: Has AllowClobber
always been a parameter, or do we need to inspect the command bits to avoid using it on versions before it was added?
I just checked and it's available in 1.0.0.1 that seems be shipped with Win10 and it's included with all versions in the PSGallery (first uploaded version: 1.1.0.0).
After pondering over it a bit I believe having an AllowClobber parameter that can be disabled for certain edge cases is a good idea.
Sweet! Will add it in as a parameter, default to present; have most of it in place
@devblackops - added this as the default, ping if it's still causing trouble!
I require
BuildHelpers
in many (most) of my modules and that module exposes the functionExport-Metadata
. I also have Joel'sConfiguration
module installed which also exposes this function. This causes frequent issues when installing/updatingBuildHelpers
. To work around this the-AllowClobber
is needed when installing the module. It would be nice if PSDepend allowed this switch to be passed toInstall-Module
.