On Wed, 4 Jan 2017 21:32:50 +0100 Arve Barsnes <arve.bars...@gmail.com> wrote:
> On 4 January 2017 at 21:25, Daniel Frey <djqf...@gmail.com> wrote: > > > I always do `emerge -uDN world`. Which is --update --deep > > --newuse... I've just never had that happen with depclean before. > > Odd, no? > > > > I usually do: > > > > `emerge -uDN world` > > > > and > > > > `emerge -ac` to depclean afterwards. > > > > As I use --deep all the time, I'm still confused as to why needed > > packages weren't installed. > > > > > I've also always used --deep, but I've seen this many times. I've > recently started using "--with-bdeps=y" as well, and I don't think > I've seen this happen since then, so I'm guessing binary deps are the > culprit. I think so too. Since Dan does not use --with-bdeps this is what might happen: 'qtdeclarative', 'qtxml' and 'qtcore' were updated from 5.6.1 to a higher version. However 'linguist-tools', being only a build dependency, was not updated and remains at version 5.6.1. Since 'linguist-tools-5.6.1' depends on 'qtdeclarative-5.6.1', 'qtxml-5.6.1' and 'qtcore-5.6.1' --depclean resolves those as missing packages. So as Arve is saying - using --with-bdeps should prevent this. There are two ways how to use it: - As 'emerge -uDN --with-bdeps=y world' - in this case build dependencies will be updated as well. - As 'emerge -ac --with-bdeps=n' - in this case build dependencies will be depcleaned (removed). Notice there is 'n' in --with-bdeps. I prefer second option since this leaves a clean system where only packages required to run it are installed. Disadvantage is that upon next update the build dependencies are emerged again, so it takes more time to update the system. Robert -- Róbert Čerňanský E-mail: ope...@tightmail.com Jabber: h...@jabber.sk
