| 1 |
On Sunday 05 April 2015 18:29:05 Andreas K. Huettel wrote: |
| 2 |
|
| 3 |
> Do you see anything that is actually broken? |
| 4 |
|
| 5 |
Apart from perl-cleaner and portage? Emerge exiting silently after being |
| 6 |
given a list of packages to emerge doesn't exactly seem like normal |
| 7 |
behaviour to me. It was told "emerge -v1 ...[list of packages]" as in perl- |
| 8 |
cleaner's usual behaviour. No ifs, no buts - just do it. |
| 9 |
|
| 10 |
> Minor updates (5.x.y -> 5.x.y+1) do not need any rebuilds or |
| 11 |
> reinstallations of modules. |
| 12 |
> |
| 13 |
> Not 100% sure what perl-cleaner does when you run it anyway. Maybe it |
| 14 |
> reinstalls all, but it's not necessary. |
| 15 |
|
| 16 |
I just ran it to see what it'd do. I got more than I'd bargained for. |
| 17 |
|
| 18 |
> [Side note, your information on what perl-cleaner does is very vague, I |
| 19 |
> can't distll anything useful out of it.] |
| 20 |
|
| 21 |
The two virtuals were perl-File-Spec-3.480.100 and perl-Storable-2.490.100. |
| 22 |
I hope you don't want me to list the hundreds of files it can't handle. |
| 23 |
|
| 24 |
-- |
| 25 |
Rgds |
| 26 |
Peter. |
Archives