| 1 |
On Sat, Nov 30, 2019 at 5:35 PM Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
|
| 3 |
> On Sat, 30 Nov 2019 16:47:35 +0000, Wols Lists wrote: |
| 4 |
> |
| 5 |
> > > There's no need to mess around adding and removing masks, just use |
| 6 |
> > > the - |
| 7 |
> > > - exclude option. |
| 8 |
> > > |
| 9 |
> > > Yep! For some reason, that option doesn’t always occur to me, but |
| 10 |
> > > that’s clearly a simpler way to do it. Thanks for reminding me! |
| 11 |
> > > |
| 12 |
> > Couldn't you just have a script that "emerge --update"s each package in |
| 13 |
> > sequence? If the package isn't due for update nothing will happen. And |
| 14 |
> > then you could follow that with an "emerge world" knowing that your hogs |
| 15 |
> > are already done. |
| 16 |
> |
| 17 |
> Sometimes the packages are rebuilt without an update, especially if you |
| 18 |
> use --changed-use or --changed-deps, so it's not quite that simple. |
| 19 |
|
| 20 |
|
| 21 |
But still pretty simple. I’ve just used the “build in sequence” idea for |
| 22 |
an update that forced a libreoffice rebuild. It first upgraded a few of |
| 23 |
libreoffice’s dependencies in parallel, and then rebuilt libreoffice by |
| 24 |
itself afterwards. A subsequent emerge @world upgraded a bunch of minor kde |
| 25 |
stuff. I like this idea - seems to isolate the “hogs” so they build one at |
| 26 |
a time, and it does so without any intervention on my part. Thanks! |
| 27 |
|
| 28 |
John Blinka |
Archives