left geyser
more assorted questions i'm curious about
-what does portage do as a package manager? i'm curious because at its core package managers actually seem like fairly simple beasts in terms of how they function, simply scanning through a list of packages in the repository and downloading them. portage appears to be significantly more complex, and as far as i'm aware it's functions are to:
pull source code from ebuild urls
find the available use flags & mask keywords for the ebuild
scan it's configuration files for overrides
compile the code with selected flags and options
detect and create package configs + change their default paths to savedconf
scan packages in world whenever a world update occurs, and update packages & their dependencies to the newest available version
provide a variety of other smaller safety and convenience features
this is obviously more than the average package manager, but i'm curious as to if there's anything i missed or that isn't actually that big of a part of portage, and how complex it really is
-why was portage written in python?
-what are the differences between portage and nix?
-what are the differences between a compiler and a build system?
-does portage use a build system?
i may have further questions