| 1 |
Looking at your patch code based on what you have just explained, |
| 2 |
|
| 3 |
I could go back and re-edit the build file and remove the extra code I |
| 4 |
added at the end restoring the file to its original state. |
| 5 |
|
| 6 |
Then I could move the cursor up to the following section of the build file: |
| 7 |
|
| 8 |
src_configure() { |
| 9 |
# gui can be built but will not be installed |
| 10 |
local emesonargs=( |
| 11 |
-Ddebug-gui=false |
| 12 |
$(meson_use doc documentation) |
| 13 |
$(meson_use input_devices_wacom libwacom) |
| 14 |
-Dtests=false # tests are restricted |
| 15 |
-Dudev-dir="$(get_udevdir)" |
| 16 |
) |
| 17 |
meson_src_configure |
| 18 |
|
| 19 |
and then replace the line -Dudev-dir="$(get_udevdir) with |
| 20 |
|
| 21 |
-Dudev-dir="${EPREFIX}$(get_udevdir) |
| 22 |
|
| 23 |
Your patch also has these lines in it: |
| 24 |
|
| 25 |
--- a/dev-libs/libinput/libinput-1.13.2.ebuild |
| 26 |
+++ b/dev-libs/libinput/libinput-1.13.2.ebuild |
| 27 |
@@ -60,7 +60,7 @@ src_configure() { |
| 28 |
|
| 29 |
are these lines suggesting that I make any other changes to the ebuild file? |
| 30 |
|
| 31 |
They look like they are saying that an ebuild file has to be changed in a |
| 32 |
particular section. |
| 33 |
|
| 34 |
If the only change I have to make is the single line above I will do it and |
| 35 |
then run the digest command and try to |
| 36 |
emerge libinput again. |
| 37 |
|
| 38 |
Regards |
| 39 |
|
| 40 |
MF |
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
On Thu, 27 Jun 2019 at 12:46, Fabian Groffen <grobian@g.o> wrote: |
| 50 |
|
| 51 |
> Haha, I gave you a patch, sorry. |
| 52 |
> |
| 53 |
> The patch just describes which change you need to make. If you really |
| 54 |
> want to have an easy life, then restore the original ebuild (rsync if |
| 55 |
> you will) and run this: |
| 56 |
> |
| 57 |
> % patch libinput-1.13.2.ebuild < path/to/the-patch-content.patch |
| 58 |
> |
| 59 |
> Then you can run ebuild .. digest. |
| 60 |
> |
| 61 |
> There is a chance the patch won't apply, because I didn't attach it. |
| 62 |
> In this case I think it's quicker if you "read" the patch yourself, find |
| 63 |
> the location what the patch is about, and make the change (as indicated |
| 64 |
> by the lines prefixed with - (removed) and + (added)). |
| 65 |
> |
| 66 |
> Does this help you? |
| 67 |
> |
| 68 |
> Fabian |
| 69 |
> |
| 70 |
> |
| 71 |
> |
| 72 |
> |
Archives