james <gar...@verizon.net> [16-07-30 20:52]: > On 07/30/2016 01:15 PM, meino.cra...@gmx.de wrote: > > >>>Short qyestion: How can I apply it...I mean...as soon as I do an > >>>emerge, either the original source will be unpacked or my package > >>>will be rejected for being modified an different from the one, which > >>>does not compile... > > >>http://tinyurl.com/jur3t8v > > >Meino > > I think that is true for EAPI-5. EAPI-6 or later ebuilds should only > require the patch be located in the dir with the sources > (/usr/portage<cat/pak> or /usr/local/portage/<cat/pak>, I think. > (epatch-users is good to google on. There might be a bit more to it, > but just google. Also, there are some eclasses that help this out a bit > for more complicated hacks. [1] > > 1] https://devmanual.gentoo.org/eclass-reference/ > > > Usually, the best thing to do is put (your) patches and a full copy of > the ebuild into /usr/local/portage, for a guy like you who is hacking > at ebuilds for embedded boards anyway. > > > proxy-maint folks are the best to answer these question and help you, > cause there are always twists and bumps along the way, like > dependencies slightly changed and thus requiring a tweak. Unfortunately > they are only available on the irc channel. Hopefully on of the devs > will clear this up even further, as last time I looked, this is a > subject that the devManual has not fully documented, or anyone compiled > a few examples for user to look at. It's a moving target depending on > the EAPI-level of the ebuild. > > > hth, > James > > Hi James,
thanks for your help ! :) Will check that... ;) Best regards, Meino
