portage-ng --merge
>>> Emerging : portage://net-proxy/haproxy-3.2.9999:run?{[]}
These are the packages that would be merged, in order:
Calculating dependencies... done!
└─step 1─┤ keyword portage://net-proxy/haproxy-3.2.9999 (**)
└─step 2─┤ download portage://net-proxy/haproxy-3.2.9999
│ └─ live ─┤ live git repository
└─step 3─┤ install portage://acct-group/haproxy-0-r3
└─step 4─┤ run portage://acct-group/haproxy-0-r3
└─step 5─┤ install portage://acct-user/haproxy-0-r3
└─step 6─┤ run portage://acct-user/haproxy-0-r3
└─step 7─┤ install portage://net-proxy/haproxy-3.2.9999 (**)
│ └─ conf ─┤ USE = "crypt pcre ssl threads* net_ns slz -lua* -zlib (-51degrees) (-wurfl) -doc -examples -pcre-jit -prometheus-exporter
│ │ -quic -test -tools"
│ │ LUA_SINGLE_TARGET = "-lua5-3 -lua5-4"
│ │ SLOT = "0/3.2"
└─step 8─┤ run portage://net-proxy/haproxy-3.2.9999
Total: 8 actions (1 keyword, 1 download, 3 installs, 3 runs), grouped into 8 steps.
0.00 Kb to be downloaded.
>>> Assumptions taken during proving & planning:
Keyword acceptance (1 package):
Add to /etc/portage/package.accept_keywords:
net-proxy/haproxy **