Suggestion: don't require `mv` overlay
The mv overlay is currently being used to provide a way to extend portage through /etc/portage/bashrc.d. This works pretty nicely for the purposes of this project, as the flag overrides file is really nice. However, I don't use this overlay, or the other features of this bashrc.d implementation, and I'd like to keep my portage's behavior as "default" as possible. Having to package.mask the overlay is a bit of a nuisance, and there's no obvious way to disable certain functionality of this bashrc.d.
That leads me to create this suggestion. It'd be nice if the ltoize ebuild could (optionally) include a stripped-down version of portage-bashrc-mv. That would ideally just include bashrcd.sh and 10-flag.sh, and have a USE flag to instead use the "full" version by depending on the ebuild in the mv overlay. This would avoid having to add an overlay full of unrelated ebuilds and unexpected portage behavior related to this bashrc.d.
i add */*::mv (or any other overlay i use for a specific package) to /etc/portage/package.mask and the unmask only the things i want
it's a healthy beahviour with any overlay @wolfwood
@wolfwood I'm aware that's a solution for my first concern, but thanks for pointing it out anyway.
Currently, I'm placing app-portage/portage-bashrc-mv in my package.provided, and installing the bashrc manually, to solve my second concern.
However, I believe both of the concerns could be solved in this repo, so it's easier to get a "clean" LTOed install.
If your concern is the other features app-portage/portage-bashrc-mv provides, you can disable USE=ccache remove-la title on it which should do just that. Indeed, sys-config/ltoize only depends on the cflags USE being set.
For some reason I hadn't seen the different USE flags in the ebuild, thanks for pointing those out. The last file, 80-localepurge.sh does nothing unless explicitly enabled in make.conf.
This all does indeed solve both of my concerns, aside from the minor inconvenience of having to set it up, and having to keep the repo around, but I guess I can live with that. Thanks.
Agree with @mid-kid