1 |
Hello Alex, |
2 |
|
3 |
2011/9/22 Alex Efros <powerman@××××××××.name>: |
4 |
> Hi! |
5 |
> |
6 |
> Today I've decided to try to switch from `cpan` to `g-cpan`. |
7 |
> I was pleasantly surprised - g-cpan have installed all ~300 perl modules I |
8 |
> need and just one module required manual .ebuild editing (Crypt-MatrixSSL). |
9 |
> I've successfully configured portage to use my local CPAN overlay, force |
10 |
> installing latests available versions for all modules, and run tests for |
11 |
> all perl modules - i.e. do exactly same what `cpan` do. |
12 |
> |
13 |
> But I don't understood how to implement equivalent of `cpan>upgrade`: |
14 |
> |
15 |
> 1) `g-cpan --cpan_reload` doesn't work at all: |
16 |
> |
17 |
> # g-cpan --cpan_reload |
18 |
> * You haven't told g-cpan what to do. |
19 |
> |
20 |
> Please consult g-cpan --help or man g-cpan for more information |
21 |
> |
22 |
> This can be worked around by running `cpan>reload index`, but it's sad |
23 |
> we can't use only `g-cpan` for all tasks and still need to run `cpan`. |
24 |
|
25 |
This mode works for me fine. What versions of perl, cpan you use ? |
26 |
|
27 |
> |
28 |
> 2) `g-cpan -u` works (after `cpan>reload index`), but it have nasty side |
29 |
> effect by adding several modules (I've no idea why exactly these |
30 |
> modules) into world file when it finish (no matter is it updated some |
31 |
> modules or not): |
32 |
> |
33 |
> >>> Recording perl-gcpan/CPAN-Reporter in "world" favorites file... |
34 |
> >>> Recording perl-gcpan/Devel-Autoflush in "world" favorites file... |
35 |
> >>> Recording perl-gcpan/Filter-CommaEquals in "world" favorites file... |
36 |
> >>> Recording perl-gcpan/IO-CaptureOutput in "world" favorites file... |
37 |
> >>> Recording perl-gcpan/Log-Report in "world" favorites file... |
38 |
> >>> Recording perl-gcpan/Test-Reporter in "world" favorites file... |
39 |
> |
40 |
> 3) `g-cpan -u` will update only modules in perl-gcpan/* category, but how |
41 |
> to automatically update modules in perl-core/* and dev-perl/*? |
42 |
> And perl core modules which are in dev-lang/perl but don't have own |
43 |
> perl-core/* package yet? |
44 |
> Or only way is first run `cpan>r` to find possible updates and then |
45 |
> manually add ebuilds for these modules into /usr/local/portage? |
46 |
|
47 |
emerge do it for you. AFAIK g-cpan designed for update only custom cpan modules. |
48 |
|
49 |
> |
50 |
> 4) How to protect against occasional overloading of newest perl core |
51 |
> module installed with new dev-lang/perl version by older versions of |
52 |
> same module installed by package perl-core/* or dev-perl/* or even |
53 |
> perl-gcpan/* (last two cases possible for modules which wasn't |
54 |
> included in previous dev-lang/perl versions)? |
55 |
> |
56 |
> P.S. I'm using latest stable app-portage/g-cpan-0.16.2. |
57 |
> |
58 |
|
59 |
Ah, see here you version. Try 0.16.4 - in this version fixed some your bugs. |
60 |
Like |
61 |
... |
62 |
24 Jan 2011; Robin H. Johnson <robbat2@g.o> +g-cpan-0.16.4.ebuild: |
63 |
Bump. Bug #352561: Allow --cpan_reload without other arguments. |
64 |
... |
65 |
|
66 |
Unfortunately, recently, g-cpan not actively develops :( |
67 |
|
68 |
-- |
69 |
Sergiy Borodych |
70 |
http://bor.org.ua |