| 1 |
On Tue, 3 Dec 2019 10:43:36 -0500, John Blinka wrote: |
| 2 |
|
| 3 |
> > > Couldn't you just have a script that "emerge --update"s each |
| 4 |
> > > package in sequence? If the package isn't due for update nothing |
| 5 |
> > > will happen. And then you could follow that with an "emerge world" |
| 6 |
> > > knowing that your hogs are already done. |
| 7 |
> > |
| 8 |
> > Sometimes the packages are rebuilt without an update, especially if |
| 9 |
> > you use --changed-use or --changed-deps, so it's not quite that |
| 10 |
> > simple. |
| 11 |
> |
| 12 |
> |
| 13 |
> But still pretty simple. I’ve just used the “build in sequence” idea |
| 14 |
> for an update that forced a libreoffice rebuild. It first upgraded a |
| 15 |
> few of libreoffice’s dependencies in parallel, and then rebuilt |
| 16 |
> libreoffice by itself afterwards. A subsequent emerge @world upgraded a |
| 17 |
> bunch of minor kde stuff. I like this idea - seems to isolate the |
| 18 |
> “hogs” so they build one at a time, and it does so without any |
| 19 |
> intervention on my part. Thanks! |
| 20 |
|
| 21 |
But if you emerge --update libreoffice before the package that is forcing |
| 22 |
the rebuild, why would libreoffice rebuild? I would expect it to only |
| 23 |
rebuild libreoffice after the dependency had been changed. |
| 24 |
|
| 25 |
I'm not saying out wouldn't work some of the time, but I can see |
| 26 |
situations where it wouldn't. Whereas |
| 27 |
|
| 28 |
emerge --opts @world --exclude memory-hogs... |
| 29 |
emerge --opts --jobs 1 @world |
| 30 |
|
| 31 |
should always isolate them. |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Neil Bothwick |
| 36 |
|
| 37 |
Hello, this is an extension to the famous signature virus, called spymail. |
| 38 |
Could you please copy me into your signature and send back what you were |
| 39 |
doing last night between 10pm and 3am? |
Archives