Why doesnt the aspell ebuild do that for you? -- here is a good enough solution: dicts=$(find /var/db/pkg/app-dicts/ -type d | grep aspell) for dict in $dicts; do package=$(basename $dict) emerge ${package%-*} done its 5 short lines of code that save many headaches (in my opinion), and the right step to be able to use GLSA to automate security updates. I do understand they should be supervised, yes, but I run glsa-check -f all twice a day automatically to make sure system stays secure and read the log files after for anything needed on my behalf and to test if changes didnt break anything -- trivial things like re-merging aspell-en however really aught to be done by the ebuild. Also, this will be consistent, there are more than several ebuilds on portage that emerge "dependencies" after the package itself is merged. Your thoughts? Reproducible: Always Steps to Reproduce:
well, if the dictionary was in your world file, then it will be upgraded if theres a new version. eg, emerge without -u.
ewarn "Please re-emerge ALL your aspell-LANG dictionaries" So its not about updating a new version. Its about re-merging the current version.
Calling emerge from within ebuild is neither allowed nor safe (race conditions, sandbox issues, etc. etc. etc.) WONTFIX.
