?- show.
See it think.
Proven plans in the terminal, interactive graphs and Gantt charts in the browser — and the builder executing a plan, phase by phase.
~ ❯ portage-ng --pretend neovim >>> Emerging : portage://app-editors/neovim-0.11.6-r2:run?{[]} Calculating dependencies... done! └─step 1─┤ download portage://dev-python/tree-sitter-0.25.2 │ └─ file ─┤ 170.27 Kb tree-sitter-0.25.2.tar.gz │ download portage://dev-lua/luv-1.50.0.1 │ download portage://dev-libs/unibilium-2.1.2 ⋮ 16 more downloads └─step 2─┤ install portage://dev-lang/lua-5.1.5-r200 (blocked: soft by dev-lang/lua) │ └─ conf ─┤ USE = "readline deprecated" │ install portage://dev-libs/tree-sitter-c-0.24.1 │ └─ conf ─┤ USE = "python -debug -test" │ │ PYTHON_TARGETS = "python3_13 -python3_12 -python3_14" │ install portage://dev-lua/mpack-1.0.13 │ └─ conf ─┤ LUA_TARGETS = "lua5-1 -lua5-3 -lua5-4 -luajit" ... └─step 7─┤ install portage://app-editors/neovim-0.11.6-r2 │ └─ conf ─┤ USE = "nvimpager -test" │ │ LUA_SINGLE_TARGET = "lua5-1 -luajit" └─step 8─┤ run portage://app-editors/neovim-0.11.6-r2 Total: 57 actions (19 downloads, 19 installs, 19 runs), grouped into 8 steps. 16.85 Mb already downloaded — nothing left to fetch. >>> Blockers added during proving & planning: [blocks B] !dev-lang/lua:0 — soft, phase: install, required by lua-5.1.5-r200 ~ ❯
~ ❯ portage-ng --build app-editors/neovim >>> Emerging : portage://app-editors/neovim-0.11.6-r2:run?{[]} Calculating dependencies... done! └─step 1─┤ download portage://dev-python/tree-sitter-0.25.2 ✓ │ └─ file ─┤ 170.27 Kb tree-sitter-0.25.2.tar.gz ✓ │ download portage://dev-lua/luv-1.50.0.1 ✓ │ └─ file ─┤ 138.72 Kb luv-1.50.0.1.tar.gz ✓ ⋮ 17 more downloads └─step 2─┤ install portage://dev-lang/lua-5.1.5-r200 ✓ │ └─ exec ─┤ ACTION = clean → setup → unpack → prepare → configure → compile → install → merge ✓ │ │ LOG = dev-lang--lua-5.1.5-r200.log │ └─ conf ─┤ USE = "readline deprecated" ... └─step 7─┤ install portage://app-editors/neovim-0.11.6-r2 ⣷ │ └─ exec ─┤ ACTION = clean → setup → unpack → prepare → configure → compile → install → merge (63%) 6/8 │ │ LOG = app-editors--neovim-0.11.6-r2.log │ └─ conf ─┤ USE = "nvimpager -test" │ │ LUA_SINGLE_TARGET = "lua5-1 -luajit" └─step 8─┤ run portage://app-editors/neovim-0.11.6-r2
~ ❯ portage-ng --search name=portage category=sys-apps portage://sys-apps/portage-9999 portage://sys-apps/portage-3.0.77-r3 portage://sys-apps/portage-3.0.77-r1 portage://sys-apps/portage-3.0.77 portage://sys-apps/portage-3.0.72-r1 pkg://sys-apps/portage-9999 ~ ❯ portage-ng --search text editor with syntax highlighting Semantic search: "text editor with syntax highlighting" 84.7% app-editors/micro Modern and intuitive terminal-based text editor 82.3% app-editors/neovim Vim-fork focused on extensibility and usability 79.1% app-editors/vim Vim, an improved vi-style text editor ~ ❯
~ ❯ portage-ng --search-bugs neovim ### Bug search Searching for "neovim" on https://bugs.gentoo.org... Found 6 bugs for "neovim": #586882 [CONFIRMED ] vim-plugin.eclass should allow for neovim as alternate DEPENDS instead of just vim/gvim https://bugs.gentoo.org/show_bug.cgi?id=586882 #612644 [UNCONFIRMED] app-vim/* Add support for neovim https://bugs.gentoo.org/show_bug.cgi?id=612644 #932671 [CONFIRMED ] app-editors/neovim-0.10.0: unresolved soname dependency on /usr/lib64/lua/5.1/lpeg.so https://bugs.gentoo.org/show_bug.cgi?id=932671 #935641 [CONFIRMED ] tree-sitter-grammar.eclass: installs neovim libraries as broken symlinks https://bugs.gentoo.org/show_bug.cgi?id=935641 #965872 [CONFIRMED ] app-editors/neovim-0.11.5 - QA Notice: Unresolved soname dependencies: https://bugs.gentoo.org/show_bug.cgi?id=965872 #967125 [UNCONFIRMED] revdep-rebuild (Python version) falsely reports app-editors/neovim as broken while legacy script does not https://bugs.gentoo.org/show_bug.cgi?id=967125 ~ ❯
~ ❯ portage-ng --upstream neovim ### Upstream version check Checking 1 package against Repology... app-editors/neovim-0.11.6-r2 — upstream: 0.11.6 (legacy) ~ ❯
~ ❯ portage-ng --pretend --explain app-editors/neovim >>> Emerging : portage://app-editors/neovim-0.11.6-r2:run?{[]} Calculating dependencies... done! Total: 57 actions (19 downloads, 19 installs, 19 runs), grouped into 8 steps. Plan explainer ready. Ask questions about the build plan. Type "quit" or "exit" to leave. explain> why is dev-lang/lua in the plan? app-editors/neovim is built with LUA_SINGLE_TARGET=lua5-1, so its Lua modules — dev-lua/luv and dev-lua/mpack — are compiled against Lua 5.1. Both depend on dev-lang/lua-5.1.5-r200, which is why the plan installs it in step 2, before anything that links against it. It carries a soft blocker against the unslotted dev-lang/lua:0; the plan orders the replacement so the conflict never materialises. explain> why is tree-sitter-c in the plan? neovim uses tree-sitter for its built-in syntax highlighting and ships each grammar as a separate package. dev-libs/tree-sitter-c-0.24.1 is a runtime dependency of app-editors/neovim, so it is installed in step 2 — built with USE="python" and PYTHON_TARGETS="python3_13" for the grammar tooling. explain>
~ ❯ portage-ng --llm claude Chat session with claude (claude-sonnet-4-6). Type "quit" or "exit" to leave. claude> how many ebuilds are in the portage tree? I'll query the knowledge base directly rather than guess: <call:swi_prolog> :- aggregate_all(count, cache:ordered_entry(portage, _, _, _, _), N), format('The portage tree contains ~D ebuilds.~n', [N]). </call:swi_prolog> --- computer ------------------------------------------------------------------ The portage tree contains 32,147 ebuilds. ------------------------------------------------------------------------------- The knowledge base holds 32,147 ebuilds — every version of every package in the configured repository, loaded in memory as indexed Prolog facts. That count comes from executing the query against the running system, not from my training data. claude>
click to enlarge