| Subject: | Circular dependency chain |
When I wrote this code CPAN.pm I decided to bail out when a circular
dependency is discovered and let humans decide how to break the loop.
I'm still convinced that this is better than a decision taken by a
program. Except I'm missing something. In this case I believe it's your
turn to break the loop:
Show quoted text
---- Unsatisfied dependencies detected during ----
---- MARCEL/Class-Accessor-Constructor-0.08.tar.gz ----
Class::Accessor::Installer [requires]
Data::Inherited [requires]
Class::Accessor::Complex [requires]
Recursive dependency detected:
Class::Accessor::Installer (have: N/A; want: 0.08)
=> MARCEL/Class-Accessor-Installer-0.08.tar.gz
=> Vim::Tag (have: N/A; requires: 0.04)
=> MARCEL/Vim-Tag-0.04.tar.gz
=> Class::Accessor::Constructor (have: N/A; requires: 0)
=> MARCEL/Class-Accessor-Constructor-0.08.tar.gz
=> Class::Accessor::Complex (have: N/A; requires: 0)
=> MARCEL/Class-Accessor-Complex-0.16.tar.gz
=> Class::Accessor::Installer (have: N/A; requires: 0).
Cannot resolve.
MARCEL/Class-Accessor-Constructor-0.08.tar.gz
[depend] -- NOT OK
perlin for perlin for perlin for per^WBerlin
:)