I like bash. But the reason is because it's ~everywhere in *NIX world. And the rare cases where there isn't bash I can use POSIX sh. It surely isn't a nice one to learn, but after many years with it I can say I know most of the features it offers. But the thing is - you don't need to know all the features of bash to write good ebuilds. Just basic knwoledge is enough. I go as far as to say that, if one reads the ebuild creation guides, he/she learns bash at the same time. Win-win. Double benefit.John R. Graham wrote:As you learn Portage better, you will probably realize the bash is the least of Portage's problems (or perhaps not a problem at all). Bash implements a Turing complete programming language, so almost by definition, it's not restrictive. But perhaps you meant something different. Ugly? Excessively terse? Not your favorite language? (It's not mine.) I could agree with all of those without thinking that it's even in the top 10 problems with Portage.helecho wrote:The bash ebuilds are also restrictive.
If ebuilds weren't bash, then what would be better? Awk? Lua? PHP? Follow systemd and have ini -style config files instead?
Yeah. I think bash based ebuilds aren't a problem.





