1 |
J. Roeleveld wrote: |
2 |
> On Sunday, November 20, 2016 05:07:03 PM Константин wrote: |
3 |
>> On Sun, Nov 20, 2016 at 01:35:46PM +0000, Peter Humphrey wrote: |
4 |
>>> On Sunday 20 Nov 2016 16:05:29 Константин wrote: |
5 |
>>>> On Sun, Nov 20, 2016 at 09:42:40AM -0300, Zhu Sha Zang wrote: |
6 |
>>>>> Maybe you need to use 'eclean-dist -d'. But, for your safe, use |
7 |
>>>>> 'eclean-dist -dp' first. |
8 |
>>>> BTW what troubles can I get from 'eclean-dist -d' ? As far as I |
9 |
>>>> understand it, re-download needed tar.gz will be the worst isn't it? |
10 |
>>> You'd think so, wouldn't you? But recently something has been going wrong |
11 |
>>> here such that 'eclean-pkg -d' removed every single package, leaving just |
12 |
>>> the directory structure. That was just after I'd spent six hours building |
13 |
>>> them |
14 |
>> Don't take me wrong it was not an objection but just a question. There |
15 |
>> are a lot of warnigns, but no explanations except 'users will not be |
16 |
>> protected in case they need to downgrade a package or re-install a |
17 |
>> previously removed package.' or similar. |
18 |
>> |
19 |
>> And thanks for example. |
20 |
> One example where this can be annoying is with packages that have fetch- |
21 |
> restriction enabled. Or, even worse, where certain versions are no longer |
22 |
> available for download. |
23 |
> |
24 |
> -- |
25 |
> Joost |
26 |
> |
27 |
> |
28 |
|
29 |
|
30 |
For those, you can use this option. |
31 |
|
32 |
-f, --fetch-restricted protect fetch-restricted files (--deep only) |
33 |
|
34 |
It only works with -d is the only problem I see with it. It would be |
35 |
nice if it would work for all of them. |
36 |
|
37 |
Dale |
38 |
|
39 |
:-) :-) |