1 |
On 27 September 2013 06:00, Kent Fredric <kentfredric@×××××.com> wrote: |
2 |
|
3 |
> |
4 |
> ie: every time there is a new iteration of Foo, one must iterate all the |
5 |
> virtuals that relate to it, and vet their need to be updated, and every |
6 |
> single update you do is just something thats easy to get wrong, when it |
7 |
> always seems to make so much more sense to say "X provides Y", especially |
8 |
> in the case where X provides a very large list of Y ( virtual/perl-* is a |
9 |
> maintenance nightmare ) |
10 |
> |
11 |
|
12 |
Also, can I make a suggestion that if we were to bring back PROVIDES=, that |
13 |
PROVIDES *NOT* be permitted to provide arbitrary $CAT/$P ? |
14 |
|
15 |
My very rusty memory of when I last saw that saw that as one sticking point. |
16 |
|
17 |
It seems to me that PROVIDES would be more useful in a different hierarchy, |
18 |
ie: |
19 |
PROVIDES="cpan-module/CLASS::MOP/1.6" or something. |
20 |
|
21 |
|
22 |
-- |
23 |
Kent |