On 5/14/21 8:11 PM, Neil Bothwick wrote:
On Fri, 14 May 2021 11:54:30 +0200, n952162 wrote:
Why does portage want to build this:
[ebuild R ] x11-apps/xmodmap-1.0.10::gentoo 0 KiB
given this, already installed:
/var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild
and these on my binary server (which is apparently not working properly
for reasons I'm trying to track down):
binpkgs/x11-apps/xmodmap-1.0.10.tbz2
distfiles/xmodmap-1.0.10.tar.bz2
When I remove these options, it doesn't want to anymore:
# --changed-use \
# --changed-deps \
# --newuse \
# --backtrack=100 \
# --deep \
Which option was it, I wonder, which triggered the build, and would it
bring me anything?
--changed-use would show the changed USE flag in the output, so it is
probably --changed-deps. The emerge man page explains just what the flag
does.
I haven't been able to find that display yet. I have found this:
* Messages for package virtual/dev-manager-0-r2:
* emerge --keep-going: virtual/dev-manager-0-r2 dropped because it
requires
* sys-apps/busybox[mdev]
Is this what you're referring to? In one build, I have tons of these,
but in a way that's confusing me now, they refer to packages that seem
to have been inexplicably dropped.
Incidentally, there is no point in using --newuse and --changed-use, the
former is a superset of the latter. I'd use only --changed-use to avoid
unnecessary rebuilds.
That's useful, thank you.
