Skip Menu |

This queue is for tickets about the Task-Moose CPAN distribution.

Report information
The Basics
Id: 83762
Status: resolved
Priority: 0/
Queue: Task-Moose

People
Owner: Nobody in particular
Requestors: thaljef [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 0.03



Subject: Task-Moose is not a Task
It seems to me that Task-Moose is not really a Task. It declares dependencies in the POD like a Bundle, rather than in the META.
Subject: Re: [rt.cpan.org #83762] Task-Moose is not a Task
Date: Mon, 4 Mar 2013 23:34:18 -0600
To: Jeffrey Ryan Thalhammer via RT <bug-Task-Moose [...] rt.cpan.org>
From: Jesse Luehrs <doy [...] tozt.net>
On Mon, Mar 04, 2013 at 10:18:39PM -0500, Jeffrey Ryan Thalhammer via RT wrote: Show quoted text
> It seems to me that Task-Moose is not really a Task. It declares > dependencies in the POD like a Bundle, rather than in the META.
No, the dependencies are declared in the Makefile.PL (and none of them are listed in META.yml because they are all optional). This is probably suboptimal, but it is also nothing like a Bundle. -doy
On Mon Mar 04 21:34:29 2013, doy@tozt.net wrote: Show quoted text
> No, the dependencies are declared in the Makefile.PL (and none of them > are listed in META.yml because they are all optional). This is > probably suboptimal, but it is also nothing like a Bundle.
Yes, I see that now. I stand corrected. I didn't even know you could do that sort of thing. Very neat! Then do you think that dynamic_config should be set in the META.yml then? I guess strictly speaking the configuration isn't really dynamic. But in terms of dependency resolution, it kinda is.
On Thu Mar 28 16:57:45 2013, THALJEF wrote: Show quoted text
> On Mon Mar 04 21:34:29 2013, doy@tozt.net wrote: >
> > No, the dependencies are declared in the Makefile.PL (and none of
> them
> > are listed in META.yml because they are all optional). This is > > probably suboptimal, but it is also nothing like a Bundle.
> > Yes, I see that now. I stand corrected. I didn't even know you could > do that sort of thing. Very neat! > > Then do you think that dynamic_config should be set in the META.yml > then? I guess strictly speaking the configuration isn't really > dynamic. But in terms of dependency resolution, it kinda is.
Is there any best practices documentation out there that describes how best to declare a Task or Bundle distribution?
CC: thaljef [...] cpan.org
Subject: Re: [rt.cpan.org #83762] Task-Moose is not a Task
Date: Sat, 6 Apr 2013 09:56:58 -0700
To: bug-Task-Moose [...] rt.cpan.org
From: Jeffrey Ryan Thalhammer <jeff [...] imaginative-software.com>
Show quoted text
> Is there any best practices documentation out there that describes how best to declare a Task or Bundle distribution?
Not that I'm aware of. And I'm not saying there is anything *wrong* with this Task. The dynamic_config flag is just a way of signaling that the META for this distribution is not static -- that prerequisites cannot be known until after the user has chosen which features to install. It seems like the right thing to do for Task-Moose.
It looks like all outstanding questions have been answered.