Skip Menu |

This queue is for tickets about the Xporter CPAN distribution.

Report information
The Basics
Id: 91856
Status: resolved
Priority: 5/
Queue: Xporter

People
Owner: pause [...] tlinx.org
Requestors: CHORNY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: (no value)
Fixed in: (no value)



Subject: cyclic dependency
P => Xporter => P -- Alexandr Ciornii, http://chorny.net
On Sat Jan 04 08:06:29 2014, CHORNY wrote: Show quoted text
> P => Xporter => P >
??? Whee do you see this? What Xporter version? P has Xporter, v0.0.5 in it's prereq_pm's, But Xporter has no run time dependencies. It does have CONFIGURE_REQUIRES -- oops... maybe they need to be TEST_REQUIRES? I'll respin Xporter and make those TEST_REQUIRES and see if that solves the prob -- or are you seeing it someplace else? thanks for the report!
Xporter has P in TEST_REQUIRES: NAME => 'Xporter', TEST_REQUIRES => => { 'Test::Simple' => '0.44', 'P' => '1.1.17', mem => '0.4.2' }, -- Alexandr Ciornii, http://chorny.net
Current output from CPAN client: Recursive dependency detected: P (have: N/A; want: 1.001020) => LAWALSH/P-1.1.20.tar.gz => Types::Core (have: N/A; requires: v0.1.3) => LAWALSH/Types-Core-0.1.3.tar.gz => Xporter (have: N/A; requires: v0.0.4) => LAWALSH/Xporter-0.0.6.tar.gz => P (have: N/A; build_requires: v1.1.17). Cannot resolve. LAWALSH/Xporter-0.0.6.tar.gz [depend] -- NOT OK -- Alexandr Ciornii, http://chorny.net
On 2014-01-04 21:14:57, LAWALSH wrote: Show quoted text
> It does have CONFIGURE_REQUIRES
That's not what CONFIGURE_REQUIRES is for. See CPAN::Meta::Spec.
On Sun Jan 05 13:36:21 2014, ETHER wrote: Show quoted text
> On 2014-01-04 21:14:57, LAWALSH wrote:
> > It does have CONFIGURE_REQUIRES -- oops... maybe they need to be TEST_REQUIRES?
> > That's not what CONFIGURE_REQUIRES is for. See CPAN::Meta::Spec.
I didn't say that was what it was for. I did read it. That's why I said maybe it needed to be TEST_REQUIRES? Are you saying that is wrong?
bug was in Xporter, so trying to move this ticket there.
This should be fixed in Xporter 0.0.9 P, which initially demonstrated the problem, has the dep on the new version in P-1.1.23. The bug came about due to a "bootstrapping enabling 'feature'[problem]", locally earlier versions of P included needed functionality from other modules and, thus, had no version dependencies on the external modules -- and could be used to build the new external modules.. The main problem came about in Xporter's tests where P was used to print diagnostic information that would have taken copying over a score or more of lines from P to provide the same functionality. Nix that idea. went with static messages and got rid of the nicer dynamic diags (which wouldn't usually be seen anyway, *sigh*). Thanks for the report -- wasn't easy to figure out why it worked in my local copies of multiple versions of perl...ug.