Looking at your patch code based on what you have just explained,
I could go back and re-edit the build file and remove the extra code I
added at the end restoring the file to its original state.
Then I could move the cursor up to the following section of the build file:
src_configure() {
# gui can be built but will not be installed
local emesonargs=(
-Ddebug-gui=false
$(meson_use doc documentation)
$(meson_use input_devices_wacom libwacom)
-Dtests=false # tests are restricted
-Dudev-dir="$(get_udevdir)"
)
meson_src_configure
and then replace the line -Dudev-dir="$(get_udevdir) with
-Dudev-dir="${EPREFIX}$(get_udevdir)
Your patch also has these lines in it:
--- a/dev-libs/libinput/libinput-1.13.2.ebuild
+++ b/dev-libs/libinput/libinput-1.13.2.ebuild
@@ -60,7 +60,7 @@ src_configure() {
are these lines suggesting that I make any other changes to the ebuild file?
They look like they are saying that an ebuild file has to be changed in a
particular section.
If the only change I have to make is the single line above I will do it and
then run the digest command and try to
emerge libinput again.
Regards
MF
On Thu, 27 Jun 2019 at 12:46, Fabian Groffen <[email protected]> wrote:
> Haha, I gave you a patch, sorry.
>
> The patch just describes which change you need to make. If you really
> want to have an easy life, then restore the original ebuild (rsync if
> you will) and run this:
>
> % patch libinput-1.13.2.ebuild < path/to/the-patch-content.patch
>
> Then you can run ebuild .. digest.
>
> There is a chance the patch won't apply, because I didn't attach it.
> In this case I think it's quicker if you "read" the patch yourself, find
> the location what the patch is about, and make the change (as indicated
> by the lines prefixed with - (removed) and + (added)).
>
> Does this help you?
>
> Fabian
>
>
>
>
