Resources are not supposed to have Resource in the module name

[TravisEz13]

No description provided.

[jianyunt]

Thanks Travis. Do you have a better name for this project?

[mgreenegit]

PackageManagement

[jianyunt]

This name is already taken. PackageManagement (a.k.a OneGet) is the package manager's aggregator, it's a Windows inbox component and upgrade-able from PowerShellgallery.com. it deals with package discovery and installation etc.
Here we are dealing with the package provider's DSC resources. So PackageManagement may not be a good name either.

[gaelcolas]

Just to add an update here, the naming convention is discussed here: PowerShell/PowerShell-RFC#10 and the DSC community calls seems to be leaning towards _ModuleName_Dsc

That would give, IMO, PackageManagementDsc
At least when converted to an HQRM resource.

[PlagueHO]

My team has been attempting to use this resource and have run into a few bugs that we are fixing. So we are planning on fixing this as well as making the changes to bring it up to HQRM. So once that is done it might be worth renaming this resource at that point.

[jianyunt]

Can you please send Pull Request for a few bugs you are fixing so that we can integrate them?
Also we are considering merge this module to the PackageManagement, therefore won't have naming problem.

[PlagueHO]

Hi @jianyunt - sure thing. I'll get the fixes up to you guys once we figure out a solution - the main problem we have is that registering a package source using DSC registers under the Local System account (I think) rather than for a specific user. This might be a case of running the LCM under a different context (using PSDscRunAsCredential), but that isn't available for WMF4.0.

[brywang-msft]

This issue was moved to OneGet/oneget#262