| 1 |
On 05/01/2014 15:06, Jarry wrote: |
| 2 |
> On 05-Jan-14 13:48, Pavel Kazakov wrote: |
| 3 |
>> On 01/05/2014 04:32 AM, Jarry wrote: |
| 4 |
>>> ... |
| 5 |
>>> I see it failed in config-phase with: |
| 6 |
>>> "error: XML::Parser perl module is required for intltool" |
| 7 |
>> |
| 8 |
>> The proper dependency should be pulled in (x11-misc/shared-mime-info |
| 9 |
>> depends on dev-util/intltool, which depends on dev-perl/XML-Parser). |
| 10 |
>> |
| 11 |
>> My guess is that you recently upgraded perl, which might require you to |
| 12 |
>> rebuild the perl modules. You can try rebuilding just |
| 13 |
>> dev-perl/XML-Parser, but I recommend using perl-cleaner [1] to rebuild |
| 14 |
>> all the modules: |
| 15 |
>> perl-cleaner --allmodules -v |
| 16 |
>> |
| 17 |
>> And then try to rebuild shared-mime-info. |
| 18 |
> |
| 19 |
> You are right and this fixed my problem. Thanks! I really updated |
| 20 |
> perl recently but I did not know I had to run perl-cleaner. Never |
| 21 |
> heard of it. Should not it be done automaticaly, always after new |
| 22 |
> perl version has been installed? |
| 23 |
> |
| 24 |
> Jarry |
| 25 |
> |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
perl ebuilds up to and including 5.14.2 used to give you an ewarn() that |
| 30 |
said to run perl-cleaner, and how to do it. I see it's missing from the |
| 31 |
5.16 series of ebuilds. |
| 32 |
|
| 33 |
I didn't look into it too closely, but I would consider this a bug. |
| 34 |
There is no easy way to just quickly discover that a module is built for |
| 35 |
a previously installed version of perl - you can poke around in |
| 36 |
/usr/lib/perl5/<version>/XML/Parser but that's not exactly easy to use. |
| 37 |
And the failures are mysterious and hard to understand. |
| 38 |
|
| 39 |
You might want to file a bug at b.g.o. about the lack of messages at the |
| 40 |
end of a perl install. |
| 41 |
|
| 42 |
The reason it is not done automatically is that it's a huge job. the |
| 43 |
scripts has to find every perl module it can, check the version it is |
| 44 |
built against and decide if it needs to be rebuilt then emerge it. This |
| 45 |
can easily be 50-100 packages or more and can take longer than to build |
| 46 |
firefox. Portage can't figure this out when emerging perl that's why it |
| 47 |
doesn't do it, it is left to you to do manually. Same with python. |
| 48 |
|
| 49 |
Golden rule: |
| 50 |
|
| 51 |
When updating perl or python and a version change occurs, take note and |
| 52 |
always run perl-cleaner or python-updater afterwards. |
| 53 |
|
| 54 |
-- |
| 55 |
Alan McKinnon |
| 56 |
alan.mckinnon@×××××.com |
Archives