[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl-qa
Subject:    Re: configure_requires and new META.yml keys
From:       David Golden <xdaveg () gmail ! com>
Date:       2009-02-19 19:34:23
Message-ID: 5d4beb40902191134i39291ec5ne0c8994ea8d9dd27 () mail ! gmail ! com
[Download RAW message or body]

On Thu, Feb 19, 2009 at 2:05 PM, Eric Wilhelm
<scratchcomputing@gmail.com> wrote:
> We do not currently have a plan for how to handle this.  It would likely
> involve some mechanism of requiring compliance to a minimum version of
> the META spec.  An old loader cannot know that it is too old.  When we
> do define some sort of "minimum META mechanism", an old loader with no
> mMm support will still never know that it is too old.
>
> This is similar to the configure_requires issue in that a tool not
> supporting c_r will fail in unknown ways.  But the mMm could have
> cleanly forced c_r support had it been present from the get-go.

That's a great point.  I've added it for discussion on the Toolchain
Roadmap page [1]

   [1] http://perl-qa.hexten.net/wiki/index.php/Toolchain_Roadmap

-- David
[prev in list] [next in list] [prev in thread] [next in thread]