2012/1/6 Wolfgang Bornath <molc...@googlemail.com>: > 2012/1/6 Thierry Vignaud <thierry.vign...@gmail.com>: >> On 6 January 2012 12:27, Wolfgang Bornath <molc...@googlemail.com> wrote: >>> This is a well known issue. >>> To clear out the list you need a deep knowledge of the system to >>> determine which packages are really not needed anymore. >>> >>> Lately this --auto-orphans line shreddered my whole system on a fresh >>> install after the first update, several system services could not >>> start at next reboot, applications did not run, etc. One of the very >>> few times I had to re-install because of a bug. Call me newbie or >>> pussy but until this is not a secure function I will never touch it >>> again. >> >> This is just a bogus claim: >> If some apps break after removing orphan packages, they'll break too >> after manually removing such packages, meaning they lack some >> requires... > > Yes, right, I'd not remove such packages manually - they were marked > as orphans and removed by the function - which is my claim.
To make it clear - my claim is that the orphan function marked packages as orphans which are needed and which I'd never remove manually. If you have a list of 100 "orphans" it is next to impossible for a normal user to sit down and check each and every package if it is really an orphan (orphan in the sense of "not needed"). -- wobo