Puppet: System Administration Automated

Support

Ticket #973 (closed defect: wontfix)

Opened 1 year ago

Last modified 1 year ago

Packages with the same name in different providers cannot be defined

Reported by: sdelmont Assigned to: luke
Priority: normal Milestone:
Component: library Version: 0.24.0
Severity: normal Keywords: packagename name provider
Cc: Triage Stage: Needs design decision
Attached Patches: Code Complexity: Unknown

Description (Last modified by luke)

If you need to install two different packages, using two different providers, that just happen to have the same name, puppet will complain about "Resource Package[whatever] is already defined"

The attached patch adds a "packagename" parameter to the Package Type that lets you override the internal name used when invoking the provider. This allows a declaration like: 

packagename { "mysql-yum":
    ensure   => installed,
    package  => "mysql",
    provider => yum;
}

packagename { "mysql-gem":
    ensure   => installed,
    package  => "mysql",
    provider => gem;
}

The patch implements support for this feature in all available package providers as of 0.24.0

Attachments

packagename.patch.0.24 (21.7 kB) - added by sdelmont on 12/27/07 21:56:53.
fix-973.patch (25.0 kB) - added by sdelmont on 12/28/07 16:20:58.

Change History

12/27/07 21:56:53 changed by sdelmont

  • attachment packagename.patch.0.24 added.

12/27/07 22:16:58 changed by sdelmont

This patch is actually not working :-(

12/28/07 15:40:46 changed by luke

  • description changed.

12/28/07 16:20:58 changed by sdelmont

  • attachment fix-973.patch added.

12/28/07 16:21:36 changed by sdelmont

Please ignore (and delete, if possible) the patch called packagename.patch.0.24

12/28/07 16:23:37 changed by sdelmont

fix-973.patch does work (at least when I tested it locally)

01/18/08 11:37:22 changed by jamtur01

  • keywords set to packagename name provider.
  • owner changed from community to luke.
  • stage changed from Unreviewed to Needs design decision.

Luke - This makes sense to me but I figure it's your call. If you agree I am happy to apply the patch.

01/28/08 04:54:31 changed by luke

  • status changed from new to closed.
  • resolution set to wontfix.

I'm not willing to apply this patch, because it makes packages behave differently than other types that support providers.

We need to make a decision about whether we consider two resources with the same name but different providers to be the same resource, and upon deciding we need to implement the necessary support for all resource types, not just one type.