On Fri, 11 Nov 2005, Will Coleda wrote:
On Nov 11, 2005, at 5:15 PM, Joshua Hoblitt wrote:
As in my original proposal, Configure.pl would have to set the order
that the steps run in. Longer term it'd be nice to build a dependency
tree between the steps and execute them in order of
On Thu, Nov 10, 2005 at 10:16:14AM +, Simon Wistow wrote:
On Wed, Nov 09, 2005 at 05:57:22PM -1000, Joshua Hoblitt said:
I've taken a look at using Module::Pluggable to register configure
steps. The simplest way to do this is to let Module::Pluggable search
through the ./config
On Thu, Nov 10, 2005 at 11:51:44AM +0100, Leopold Toetsch wrote:
Joshua Hoblitt wrote:
I've taken a look at using Module::Pluggable to register configure
steps. The simplest way to do this is to let Module::Pluggable search
through the ./config directory. This requires renaming all of the
On Nov 11, 2005, at 5:15 PM, Joshua Hoblitt wrote:
On Thu, Nov 10, 2005 at 11:51:44AM +0100, Leopold Toetsch wrote:
Joshua Hoblitt wrote:
I've taken a look at using Module::Pluggable to register configure
steps. The simplest way to do this is to let Module::Pluggable
search
through the
On 11/11/05, Joshua Hoblitt [EMAIL PROTECTED] wrote:
I think it makes sense to rename the files to be .pm anyways as they're
already more of a module then a script and will only become more so.
please rename them, as we discussed on #parrot. they can't be run as
standalone scripts, so the .pl
On Fri, Nov 11, 2005 at 05:17:30PM -0500, Will Coleda wrote:
On Nov 11, 2005, at 5:15 PM, Joshua Hoblitt wrote:
As in my original proposal, Configure.pl would have to set the order
that the steps run in. Longer term it'd be nice to build a dependency
tree between the steps and execute
On Fri, Nov 11, 2005 at 02:26:13PM -0800, jerry gay wrote:
On 11/11/05, Joshua Hoblitt [EMAIL PROTECTED] wrote:
I think it makes sense to rename the files to be .pm anyways as they're
already more of a module then a script and will only become more so.
please rename them, as we discussed
Joshua Hoblitt wrote:
I've taken a look at using Module::Pluggable to register configure
steps. The simplest way to do this is to let Module::Pluggable search
through the ./config directory. This requires renaming all of the .pl
configure files to .pm because of hardwired assumptions in
On Wed, Nov 09, 2005 at 05:57:22PM -1000, Joshua Hoblitt said:
I've taken a look at using Module::Pluggable to register configure
steps. The simplest way to do this is to let Module::Pluggable search
through the ./config directory. This requires renaming all of the .pl
configure files to .pm
I've taken a look at using Module::Pluggable to register configure
steps. The simplest way to do this is to let Module::Pluggable search
through the ./config directory. This requires renaming all of the .pl
configure files to .pm because of hardwired assumptions in
Module::Pluggable.
This is a
Hi Folks,
I don't think it's worth reviewing everything that's untidy about the
current configure systems; it should be pretty obvious from looking at
the code that it needs refactoring. This isn't a criticism of the
original authors, just that the system has out grown it's roots as
'throw away'
11 matches
Mail list logo
