This came up in a bug report with the alsa-lib ebuild. Instead of having an error message printing out saying that the user has to manually apply a patch why not just have portage come out with a message saying something like "Portage must change /path/to/file, /path/to/another/file, and /path/to/another are you sure you want to continue?" This way the patch will be applied right away and people dont have to type in all the commands. Reproducible: Always Steps to Reproduce:
Err... portage instructs people to manually patch src?
Ya and I was thinking it would just be easier to have portage do it automaticly instead of manually.
Where and when does it say so?
Look at this bug report http://bugs.gentoo.org/show_bug.cgi?id=55750
That's a configure script spitting out info; couple of issues- A) no way to catch that patch as it's spit, and apply it B) violate QA if alsa-lib goes and modifies asound.h C) it would get utterly insane from a QA standpoint if portage stepped in and starting applying patches that the ebuild knows nothing about I could see adding a check to alsa-lib for configure bailing, and stating "upgrade alsa-driver or your kernel sources", but what you're after violates QA and isn't even remotely easy to do :) Closing, since (personally) I view it as a package spitting info it shouldn't be.
