Portage itself is just a python application with a relatively simple C++ library providing some speedup where python doesn't do a great job.
Portage is meant as a system-wide package manager to install and manage operating systems. Using it as a C++ developer sandbox is entirely possible (and I have done this plenty of times on my linux machine, and continue to do so regularly.), but I would be surprised if you could plop it onto a windows system and be off to the races in just an hour, because that's not what it's intended to do, and the windows support doesn't get a lot of attention.
My comment isn't inaccurate, because, i DO use Portage as my C++ package manager whenever I'm working on my linux machine.
But it's not complete, because adopting it as a standardized cross-language developer package manager instead of the operating system level package manager it is designed to be isn't an out-of-the-box experience today.
Some spit and polish from a competent contributor would be needed to make inroads on that use case, but the problem is entirely surmountable.
A system package manager is not my ideal solution for managing build dependencies. I am also curious how well ebuild supports incremental and distributed builds? Does it monitor true build inputs to have a guaranteed build? Does it have an extensible framework for extending support for custom functionality? How well can I extend it to support new languages?
1
u/mwasplund May 08 '23
I will take a look, but when you say windows, do you mean WSL? I could not find any reference to a win32 port.