"Mark Overmeer via RT" <bug-XML-Compile-WSDL11@rt.cpan.org> writes:
Show quoted text> Hum.... well, yes. Maybe you know an other solution. I split the
> WSDL11 module off, from the SOAP11 module. WSDL11 requires SOAP11.
> When you upgrade SOAP11, you need to upgrade WSDL11 when it is installed
> because the internal interface changed (slightly).
Moose has the same problem. When they break something they tell you
during installation that you'll have to upgrade also Module1..ModuleN. I
think they add these modules as "recommends". But the Recommends support
in CPAN.pm is not yet landed, it's in the trunk but does not work yet,
will probably be backed out. Even if it were there, you cannot rely on
it because people are free to (not) follow recommendations.
Some runtime warning?
Show quoted text> So, the two-way dependency is what I want. Do all installation tools
> break now? Is there an better solution?
I know that cpanplus breaks circular dependencies and installs all
modules in the circle somehow. I don't know about cpanm, sorry.
--
andreas