I think that in certain contexts it could help a lot to know before the compilation which packages will be affected by custom patches. I don't know if it happens to anyone else, but sometimes I forget that I have certain patches or forget to move them from /etc/portage/patches before the emerge so this may help to save some time. (Specially with EMERGE_DEFAULT_OPTS="--quiet-build=y" in the make.conf in which case there is no notice somewhere that a local custom patch was applied) A simple indicator should be more than enough. Reproducible: Always Steps to Reproduce: emerge -av, emerge -pv, etc. Actual Results: For example: # emerge -pv kwin These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] kde-plasma/kwin-5.26.5:5::gentoo USE="handbook lock plasma screencast -accessibility -caps -debug-gles2-only -multimedia -test" 0 KiB Expected Results: # emerge -pv kwin These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] kde-plasma/kwin-5.26.5:5::gentoo with_localpath USE="handbook lock plasma screencast -accessibility -caps -debug-gles2-only -multimedia -test" 0 KiB The expected result is just an example to illustrate what I mean in the description, but it could be some more proper string or even a single character. Thanks.
I meant 'localpatch' on the example, no 'localpath' > Calculating dependencies... done! > [ebuild R ~] kde-plasma/kwin-5.26.5:5::gentoo with_localpath > USE="handbook lock plasma screencast -accessibility -caps -debug-gles2-only > -multimedia -test" 0 KiB
This certainly makes sense to me. Would you like to try making a patch?
I wonder if it makes more sense to add another indicator in the [...] block.
