| Summary: | [g-cpan] g-cpan.pl --generate option doesn't generate ebuild... | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Ruslan U. Zakirov <Ruslan.Zakirov> |
| Component: | Tools | Assignee: | Gentoo Perl team <perl> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | mcummings, Ruslan.Zakirov |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | g-cpan | ||
| Package list: | Runtime testing required: | --- | |
The assumption here was that if you have the module installed, you've already used portage/g-cpan to generate the ebuild. Otherwise you did the install on your own (say, via cpan), which defeats the purpose of g-cpan in the first place. I'm not convinced this is a bug yet. Can you elaborate with a good (convincing) case example? (In reply to comment #1) > The assumption here was that if you have the module installed, you've already > used portage/g-cpan to generate the ebuild. Otherwise you did the install on > your own (say, via cpan), which defeats the purpose of g-cpan in the first > place. I'm not convinced this is a bug yet. Can you elaborate with a good > (convincing) case example? Reasons why I find this bad: 1) I couldn't [re]generate ebuild if module is installed via cpan or g-cpan 2) it's not consistent with emerge tool, for example I can run `emerge installed-package` and it's doing what I want re-emerges package, that's it. People need this functionality when they've installed new compiller 3) also I expected next behaviour: * `g-cpan -g Foo` [re]generates ebuild for Foo and all its dependecies, and if module is installed this command generates ebuilds for installed versions only * `g-cpan -gu Foo` generates ebuilds for latest available versions Anyway if we'll discuss and find some solution that would allow this tool to be more flexible (it's allready most flexible bridge between CPAN and distros' package systems I ever seen) I can help you to implement it. I still don't think this is a bug. However, that said, the newer versions of g-cpan don't perform the same module checks that the original g-cpan performed, so that issue might be moot. either way, i'm closing this out as won't fix - its a feature still in my mind. |
Hi, g-cpan.pl --generate option doesn't generate ebuild if user has module installed. Next block in sub install_module is responsible: elsif ( !defined $recursive && module_check($module_name) ) { print_warn ("Module already installed for '$module_name'"); return; } I find this behaviour buggy because it doesn't allow users to do what they want.