headers
Andreas J. Koenig | 13 Apr 2008 11:30
Picon

Re: optional_features

>>>>> On Tue, 18 Mar 2008 17:56:14 +1100, Adam Kennedy <adamkennedybackup <at> gmail.com> said:

  > configure_requires MUST be static, and can NEVER be programmatic.
  > That's why it exists in the first place.

It seems we must split the discussion into two or three. I'll revisit
the topic if configure_requires can be dependent on a feature once we
have gone one step further.

So let's please address now the really urgent issue of an imho blatant
spec bug. Revised patch follows.

Index: META-spec.pod
===================================================================
--- META-spec.pod	(Revision 11071)
+++ META-spec.pod	(Arbeitskopie)
 <at>  <at>  -259,13 +259,13  <at>  <at> 
 Example:

   optional_features:
-  - foo:
+    foo:
       description: Provides the ability to blah.
       requires:
         Data::Dumper: 0
         File::Find: 1.03

-I<(Spec 1.1) [optional] {map} A YAML sequence of names for optional features
+I<(Spec 1.1) [optional] {map} A YAML mapping of names for optional features
 which are made available when its requirements are met. For each
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ken Williams | 13 Apr 2008 16:14
Picon
Gravatar

Re: optional_features

On Sun, Apr 13, 2008 at 4:30 AM, Andreas J. Koenig
<andreas.koenig.7os6VVqR <at> franz.ak.mind.de> wrote:
>
>  I hope this is obvious enough for everybody to agree.

Yes - thanks, I've applied the change.

 -Ken
Permalink | Reply | 0 comments |

Gmane