| 1 |
On Sat, 14 Feb 2015 11:33:49 +0000 |
| 2 |
Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> Hello list, |
| 5 |
> |
| 6 |
> What is perl-cleaner objecting to here? It all seems pretty anodyne |
| 7 |
> to me: |
| 8 |
> |
| 9 |
> $ alias perl-cleaner |
| 10 |
> alias perl-cleaner='sudo perl-cleaner --all -- --ask --usepkg |
| 11 |
> --jobs=3 --keep-going' $ perl-cleaner |
| 12 |
> |
| 13 |
> *************************************************************************** |
| 14 |
> You are supplying additional command line options for the package |
| 15 |
> manager. This is NOT RECOMMENDED, not tested, and may lead to |
| 16 |
> incorrect, incomplete, confusing, and/or nonfunctional results. You |
| 17 |
> are on your own now. |
| 18 |
> *************************************************************************** |
| 19 |
> |
| 20 |
|
| 21 |
You are using something which is not recommended by developers, that is |
| 22 |
'-- <extra portage parameters>', telling perl-cleaner to pass |
| 23 |
additional package manager parameters, not sure why is not recommended, |
| 24 |
but it warns you, also in 'perl-cleaner --help' or man page it says it |
| 25 |
is not recommended to do that. |
| 26 |
|
| 27 |
There is probably case when you can do |
| 28 |
something wrong, but also it can be safe too passing some parameters |
| 29 |
which don't affect build like '--ask'. |
| 30 |
One case which may be problematic (or not, just guessing) is --jobs=N, |
| 31 |
what will happen if one perl module depend on the other, and they are |
| 32 |
building at the same time? |
Archives