Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do I find a source tar ball URI from CPAN::Common::Index retval? #5

Open
tokuhirom opened this issue Feb 28, 2014 · 4 comments
Open

Comments

@tokuhirom
Copy link
Member

CPAN::Common::Index returns the value in following form.

    {
      package => 'MOOSE',
      version => '2.0802',
      uri     => "cpan:///distfile/ETHER/Moose-2.0802.tar.gz"
    }

In this case, I can detect the tar ball path is http://www.cpan.org/authors/id/E/ET/ETHER/Moose-2.0802.tar.gz.
But in ExtUtils::CBuilder, tar ball path is http://ftp.riken.jp/lang/CPAN/authors/id/A/AM/AMBS/ExtUtils/ExtUtils-CBuilder-0.280210.tar.gz. How do I find a source tar ball path from return value?

@dagolden
Copy link

dagolden commented Mar 1, 2014

I don't understand the question about ExtUtils::CBuilder. Can you give me a code sample showing what you mean? Generally, the bit after cpan:///distfile should be sufficient to determine the tarball under any CPAN mirror.

Eventually, the plan is to enhance URI::cpan to give you a CPAN path directly. I might work on that at the QA hackathon.

@tokuhirom
Copy link
Member Author

I want to get a tar ball URI from URI::cpan object. But I can't get the tar ball URI from URI::cpan.

Ah, URI::cpan doesn't provide the feature yet?
... I'm waiting URI::cpan enhancement :)

@tokuhirom
Copy link
Member Author

Ah, sorry. my code has a bug...

@dagolden dagolden reopened this Mar 1, 2014
@dagolden
Copy link

dagolden commented Mar 1, 2014

I'm going to leave this open to remind me to make this easier when I'm at the QA hackathon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant