portage-ng / portage / app-admin / vaultwarden / 9999
portage-ng --merge
>>> Emerging : portage://app-admin/vaultwarden-9999:run?{[]}

These are the packages that would be merged, in order:

Calculating dependencies... done!

 └─step  1─┤ keyword portage://app-admin/vaultwarden-9999 (**)

 └─step  2─┤ download  portage://app-admin/vaultwarden-9999
             │           └─ live ─┤ live   	 git repository
             │ download  portage://www-apps/vaultwarden-web-2026.7.0
             │           └─ file ─┤ 34.64 Mb  	 vaultwarden-web-2026.7.0.tar.gz

 └─step  3─┤ install   portage://acct-group/vaultwarden-0
             │ install   portage://www-apps/vaultwarden-web-2026.7.0

 └─step  4─┤ run       portage://acct-group/vaultwarden-0
             │ run       portage://www-apps/vaultwarden-web-2026.7.0

 └─step  5─┤ install   portage://acct-user/vaultwarden-0

 └─step  6─┤ run       portage://acct-user/vaultwarden-0

 └─step  7─┤ install   portage://app-admin/vaultwarden-9999 (**)
             │           └─ conf ─┤ USE = "sqlite* web -cli -debug -mysql -postgres"

 └─step  8─┤ run     portage://app-admin/vaultwarden-9999

Total: 11 actions (1 keyword, 2 downloads, 4 installs, 4 runs), grouped into 8 steps.
       34.64 Mb to be downloaded.


>>> Assumptions taken during proving & planning:

  Keyword acceptance (1 package):
  Add to /etc/portage/package.accept_keywords:
    app-admin/vaultwarden **


Wall time
0.022 s