Tried to install app-emulation/virtualbox-additions with "-v --jobs=3" and the license doesn't show up. So it is impossible to install such packages with --jobs. W/o --jobs everything is fine.
What makes everything worse is that in case of cancelling the merge, while is not shown up, the courser is hidden afterwards.
What I wanted to say, term echoing is still off.
This problem is parallel (hehe) to the one about which I was about to file a bug. Basically, check_license needs to be updated to do nothing when it finds a portage version that supports license filtering. When was license filtering introduced? When was --jobs introduced?
License filtering first appeared in 2.2_pre1 and --jobs first appeared in 2.2_rc2.
Excellent! Since we want to skip the license check, entirely, for versions of portage which implement license filtering, all that should need to be done is: check_license() { + # Newer portage versions support license filtering. + has_version ${ROOT} >=sys-apps/portage-2.2_pre1 && return 0 local lic=$1 Zac, wouldn't you agree? Also, do you know if the other package managers support license filtering? If so, we'd probably want to extend the check to the appropriate version of those tools, too.
Due to compatibility issues, we need to define all the license groups and use them to define the default ACCEPT_LICENSE in the profile before we can enable license masking as it's intended. After we've got the license groups and ACCEPT_LICENSE, we can release a new version of portage that is reliant upon them.
It think what we should probably do is set PROPERTIES=interactive in all the check_license() ebuilds for now. That solves the immediate problem (same as bug 233296). Once we have the license groups configured in the profiles, and the required version of portage is marked stable, we can tweak check_license() as suggested in comment #5 and remove PROPERTIES=interactive from the ebuilds.
We can remove PROPERTIES=interactive from the check_license() ebuilds after portage-2.1.7.x is marked stable, approximately 1 month from now.
I'm marking this as fixed since any ebuilds that call check_license with EAPI < 3 should have PROPERTIES=interactive set. For EAPI >= 3, PROPERTIES=interactive is unnecessary due to ACCEPT_LICENSE support. See bug 299095, comment #2.