I tried to back port a KGpg krash and therefore I putted the KDEs diff file into the directory /etc/portage/patches/kde-base/kgpg-4.8.1/ : changeset_r42f8b1b51b09cb4b64fadf7e6cdd5ce359b0fa74.diff But it was ignored. From the log file of portage : >>> Preparing source in /var/tmp/portage/kde-base/kgpg-4.8.1/work/kgpg-4.8.1 ... * Applying user patches from /etc/portage/patches//kde-base/kgpg-4.8.1 ... * Done with patching >>> Source prepared. After I renamed it to 42f8b1b5.patch epatch worked well : >>> Preparing source in /var/tmp/portage/kde-base/kgpg-4.8.1/work/kgpg-4.8.1 ... * Applying user patches from /etc/portage/patches//kde-base/kgpg-4.8.1 ... * 42f8b1b5.patch ... [ ok ] * Done with patching >>> Source prepared. Reproducible: Always
I don't think the filename length is important here, but its format is, combined with some KDE related eclasses.
epatch_user() in eutils.eclass only applies patches whose names end with ".patch" (EPATCH_SUFFIX="patch"), so *.diff don't work.
(In reply to comment #2) > epatch_user() in eutils.eclass only applies patches whose names end with > ".patch" (EPATCH_SUFFIX="patch"), so *.diff don't work. Argh - is this documented (I didn't found anythign related to suffix restrictions here : http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?style=printable&part=3&chap=6#doc_chap6) ? Nevertheless what's about adding ".diff" too to the suffix list - it is a common file suffix for such things, isn't it ?
http://sources.gentoo.org/eclass/eutils.eclass?r1=1.386&r2=1.387
