On Sunday 19 Feb 2017 09:01:55 Gevisz wrote: > On Sat, 18 Feb 2017 23:15:33 +0000 Neil Bothwick <n...@digimed.co.uk> wrote: > > On Sat, 18 Feb 2017 17:01:52 +0200, Gevisz wrote: > > > > I think the problem is that you don't allow chromium to be rebuilt, > > > > because all your blocking packages depend on the installed slot > > > > (indicated by the '=') and need to be rebuilt in case ffmpeg is > > > > upgraded. So, if you don't exclude chromium ffmpeg should be upgraded > > > > and the blocking packages rebuilt/upgraded. > > > > > > Yes, you are right: with chromium everything started to compile without > > > dependency conflicts. But chromium takes more than 8 hours on my > > > computer to compile. :( > > > > Well, the newer ffmpeg was required by vlc, so you could have tried > > excluding that too. But chromium does take a while, although using ccache > > makes a big difference here. > > > > 8 hours isn't that much of a problem anyway, just start it before you go > > to bed. > > I started the compilation at about 17:00 local time. > Then I went to bed and already went out of bed. > And it still compiling, currently chromium, already for 17 hours. :(
Unless you have a lot of RAM (more than 8G) you will find that a chromium update starts swapping to disk. This slows things down. ccache does help a little, but for minor updates, or re-emerging chromium only. If you have not updated Chromium in a while you in for a long haul. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
