| 1 |
On Sat, 26 Sep 2015 15:51:07 +0200, lee wrote: |
| 2 |
|
| 3 |
> + need to rebuild (large) packages (like libreoffice) which I expect to |
| 4 |
> be upgraded and thus get rebuilt later anyway (to keep the package |
| 5 |
> management happy because it cannot figure this out for us and give us |
| 6 |
> a choice to upgrade these (large) packages as well while we are at |
| 7 |
> it), |
| 8 |
|
| 9 |
They need to be rebuilt because a package they used has updated with a |
| 10 |
changed API, poppler is the usual culprit here. It's an issue with all |
| 11 |
distros, but for the binary one it's only an issue for the devs, they |
| 12 |
build a set of packages that work together and you get to install them. |
| 13 |
If a poppler update requires a new libreoffice package, the usual choice |
| 14 |
is to skip the new poppler until a new LO is released. |
| 15 |
|
| 16 |
> + have to do other things to keep the system up to date we somehow don't |
| 17 |
> know about, like 'emerge -a --changed-deps=y @world' (because the |
| 18 |
> package management doesn't really know how to update the whole system |
| 19 |
> to begin with (because it's so complicated))? |
| 20 |
|
| 21 |
It's not that it is complicated but time-consuming. Options like |
| 22 |
--changed-deps and --with-bdeps upgrade packages that don't really need |
| 23 |
it, so why enable them by default. They not only increase the time needed |
| 24 |
to compile everything but slow down portage's dependency resolution. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
Favorite Windoze game: Guess what this icon does? |
Archives