portage-ng --merge
>>> Emerging : portage://dev-cpp/eigen-5.0.9999:run?{[]}
These are the packages that would be merged, in order:
Calculating dependencies... done!
└─step 1─┤ unmask portage://dev-cpp/eigen-5.0.9999
│ keyword portage://dev-cpp/eigen-5.0.9999 (**)
└─step 2─┤ download portage://dev-cpp/eigen-5.0.9999
│ └─ live ─┤ live git repository
└─step 3─┤ update portage://dev-cpp/eigen-5.0.9999 (**)
│ └─ conf ─┤ USE = "openmp (-blas) (-lapack) (-metis) (-opengl) (-pastix) (-test) -adolc -boost -cholmod -cuda -cuda-clang% -debug
│ │ -doc -fftw -hip -klu -mathjax -pocketfft% -sparsehash -spqr -superlu -umfpack"
│ │ CPU_FLAGS_X86 = "avx avx2 avx512dq avx512f f16c fma3 popcnt sse* sse2* sse3* sse4_1 sse4_2* ssse3*"
│ │ LLVM_SLOT = "22%* -21% -23%"
│ │ SLOT = "3/5.0"
└─step 4─┤ run portage://dev-cpp/eigen-5.0.9999
Total: 5 actions (1 unmask, 1 keyword, 1 download, 1 update, 1 run), grouped into 4 steps.
0.00 Kb to be downloaded.
>>> Assumptions taken during proving & planning:
Keyword acceptance (1 package):
Add to /etc/portage/package.accept_keywords:
dev-cpp/eigen **
Package unmask (1 package):
Add to /etc/portage/package.unmask:
=dev-cpp/eigen-5.0.9999