Re: Conflicts in the meta spec

2013-04-18 Thread Jens Rehsack
On 17.04.13 20:43, Michael G. Schwern wrote: On 4/15/13 7:06 PM, Jens Rehsack wrote: On 15.04.13 18:56, Michael G. Schwern wrote: TL;DR version... IMO we only need to clarify what "conflicts" means and what actions CPAN tools should take. We talked in the Consensus Dome about the need for and

Re: Conflicts in the meta spec

2013-04-17 Thread Michael G. Schwern
On 4/15/13 7:06 PM, Jens Rehsack wrote: > On 15.04.13 18:56, Michael G. Schwern wrote: >> TL;DR version... >> IMO we only need to clarify what "conflicts" means and what actions CPAN >> tools should take. >> >> We talked in the Consensus Dome about the need for and meaning of the >> "conflicts" rel

Re: Conflicts in the meta spec

2013-04-16 Thread Jens Rehsack
On 15.04.13 18:56, Michael G. Schwern wrote: TL;DR version... IMO we only need to clarify what "conflicts" means and what actions CPAN tools should take. We talked in the Consensus Dome about the need for and meaning of the "conflicts" relationship in the CPAN::Meta::Spec. https://metacpan.org/m

Re: Conflicts in the meta spec

2013-04-15 Thread Michael G. Schwern
On 4/15/13 7:02 PM, Mike Doherty wrote: > This requires Moose maintainers to know about all the things their > releases break. Have you considered reversing the directionality so > MooseX::Blah knows about the things which break it? That seems like a > more likely scenario to me, and lets the right

Re: Conflicts in the meta spec

2013-04-15 Thread Jan Dubois
On Mon, Apr 15, 2013 at 11:02 AM, Mike Doherty wrote: > On 13-04-15 01:56 PM, Michael G. Schwern wrote: >> >> Why we need this, why you can't do it with "requires" is because this is >> for modules which you do not depend on. Often they depend on you. >> MooseX::Blah depends on Moose, so Moose de

Re: Conflicts in the meta spec

2013-04-15 Thread Mike Doherty
On 13-04-15 01:56 PM, Michael G. Schwern wrote: Why we need this, why you can't do it with "requires" is because this is for modules which you do not depend on. Often they depend on you. MooseX::Blah depends on Moose, so Moose declares conflict with versions of MooseX::Blah it breaks. This req

Conflicts in the meta spec

2013-04-15 Thread Michael G. Schwern
TL;DR version... IMO we only need to clarify what "conflicts" means and what actions CPAN tools should take. We talked in the Consensus Dome about the need for and meaning of the "conflicts" relationship in the CPAN::Meta::Spec. https://metacpan.org/module/CPAN::Meta::Spec#Prereq-Spec IIRC the co