| 1 |
On Fri, 14 May 2021 11:54:30 +0200, n952162 wrote: |
| 2 |
|
| 3 |
> Why does portage want to build this: |
| 4 |
> |
| 5 |
> [ebuild R ] x11-apps/xmodmap-1.0.10::gentoo 0 KiB |
| 6 |
> |
| 7 |
> given this, already installed: |
| 8 |
> |
| 9 |
> /var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild |
| 10 |
> |
| 11 |
> and these on my binary server (which is apparently not working properly |
| 12 |
> for reasons I'm trying to track down): |
| 13 |
> |
| 14 |
> binpkgs/x11-apps/xmodmap-1.0.10.tbz2 |
| 15 |
> distfiles/xmodmap-1.0.10.tar.bz2 |
| 16 |
> |
| 17 |
> When I remove these options, it doesn't want to anymore: |
| 18 |
> |
| 19 |
> # --changed-use \ |
| 20 |
> # --changed-deps \ |
| 21 |
> # --newuse \ |
| 22 |
> # --backtrack=100 \ |
| 23 |
> # --deep \ |
| 24 |
> |
| 25 |
> Which option was it, I wonder, which triggered the build, and would it |
| 26 |
> bring me anything? |
| 27 |
|
| 28 |
--changed-use would show the changed USE flag in the output, so it is |
| 29 |
probably --changed-deps. The emerge man page explains just what the flag |
| 30 |
does. |
| 31 |
|
| 32 |
Incidentally, there is no point in using --newuse and --changed-use, the |
| 33 |
former is a superset of the latter. I'd use only --changed-use to avoid |
| 34 |
unnecessary rebuilds. |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Neil Bothwick |
| 39 |
|
| 40 |
WinErr 004: Erroneous error - Nothing is wrong |
Archives