| 1 |
On Wednesday 26 Apr 2017 11:51:54 Ian Zimmerman wrote: |
| 2 |
> On 2017-04-26 10:53, Peter Humphrey wrote: |
| 3 |
> > # revdep-rebuild --library 'libstdc++.so.6' -- --exclude="gcc gentoo- |
| 4 |
> > sources" --jobs --load-average=48 |
| 5 |
> > |
| 6 |
> > ...only to find that gentoo-sources was indeed emerged, though gcc |
| 7 |
> > wasn't. What's gone wrong here? I've always found that style of |
| 8 |
> > specifying exclusions to work before. |
| 9 |
> |
| 10 |
> How does gentoo-sources depend on libstdc++ ?? |
| 11 |
> |
| 12 |
> My guess is that it doesn't, and that it wouldn't have been emerged had |
| 13 |
> you not mentioned it at all. I think revdep-rebuild does some dumb |
| 14 |
> string substitution when constructing the emerge command line, such that |
| 15 |
> gentoo-sources ends up being an atom name rather than exclusion. |
| 16 |
|
| 17 |
The reason I mentioned gentoo-sources on the command line is that I'd |
| 18 |
already tried revdep-rebuild without mentioning it, with the same result |
| 19 |
(gentoo-sources emerge started), and I was trying to prevent it and avoid |
| 20 |
the waste of resources. |
| 21 |
|
| 22 |
> Maybe |
| 23 |
> |
| 24 |
> --exclude gcc --exclude gentoo-sources |
| 25 |
> |
| 26 |
> would work? |
| 27 |
|
| 28 |
Nope. I tried that too. I just had to wait while all that pointless work was |
| 29 |
done again. |
| 30 |
|
| 31 |
-- |
| 32 |
Regards |
| 33 |
Peter |
Archives