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