On Wednesday, October 8, 2014 11:51:32 AM UTC-7, John Bollinger wrote:
>
>
>
> On Wednesday, October 8, 2014 6:55:19 AM UTC-5, Felix Frank wrote:
>>
>>
>>
>> If I understand Andy correctly, we might have something like
>>
>> package { 'mysql-gem': package_name => mysql, provider => gem }
>>
>> ...which is awful I guess. Anyway, relationship targets will not be
>> jeopardized (that I can see).
>>
>
>
> It is more than awful. It either overloads the package title in dangerous
> ways, or else it deeply undermines Puppet's protections against duplicate
> resources. Consider, what is the meaning of this:
>
> package { 'mysql-gem': package_name => 'mysql', provider => 'yum' }
> ?
>
> Does it duplicate any or all of these resources?
>
> package { 'mysql-yum': package_name => 'mysql', provider => 'yum' }
> package { 'mysql-rpm': package_name => 'mysql', provider => 'rpm' }
> package { 'mysql-gem': package_name => 'mysql' }
> ?
>
Under Andy's proposal, the declaration about would duplicate the last
declaration in the list, based on a title collision.
Do the the above Package['mysql-yum'] and Package['mysql-rpm'] conflict
> with each other? (They should.)
>
> I can come up with bunches of similar issues.
>
However, this does require an act of intention on the part of the user to
set "name" to a value that is different from "title". Is there a major risk
of accidentally creating duplicate resources? Would the resulting catalog
fail in a way that obscured the source of the problem?
To me, this proposal seams like the most pragmatic way to alleviate the
problem without a major retool of how the Package type works. At the
moment, I'm not convinced that opening up the possibility of accidental
misuse outweighs the current issues surrounding the workarounds people have
to use in order to install a package and a gem that happen to share the
same name.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/628b3920-3190-4b0c-a693-f0eb8bb1ab17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
