| 1 |
Sorry for double-posting but I again forgot to sent it to the gentoo-user list. |
| 2 |
|
| 3 |
2016-01-07 13:28 GMT+02:00 Stroller <stroller@××××××××××××××××××.uk>: |
| 4 |
> |
| 5 |
>> On Wed, 6 January 2016, at 8:58 p.m., gevisz <gevisz@×××××.com> wrote: |
| 6 |
>> ... |
| 7 |
>>> If you run `sudo ebuild /usr/portage/app-misc/gtypist/gtypist-2.9.5.ebuild unpack` |
| 8 |
>>> you should be able to find the file with that line. |
| 9 |
>> |
| 10 |
>> I did it, and the ebuild has been unpacked to |
| 11 |
>> /var/tmp/portage/app-misc/gtypist-2.9.5/work |
| 12 |
>> |
| 13 |
>>> The "/*" and "*/" make that line into a comment, so "uncomment" it [3] by removing them. Save the file. |
| 14 |
>> |
| 15 |
>> Did it in the file |
| 16 |
>> /var/tmp/portage/app-misc/gtypist-2.9.5/work/gtypist-2.9.5/src/gtypist.c. |
| 17 |
>> |
| 18 |
>>> Now you should be able to run `sudo ebuild /usr/portage/app-misc/gtypist/gtypist-2.9.5.ebuild install` |
| 19 |
>>> to install gtypist with the modified code. |
| 20 |
>> |
| 21 |
>> Did it as well, though without understanding why this command should |
| 22 |
>> take into account the changes I had done in the file |
| 23 |
>> /var/tmp/portage/app-misc/gtypist-2.9.5/work/gtypist-2.9.5/src/gtypist.c |
| 24 |
> |
| 25 |
> To address where you say "without understanding" - when you emerge a package, |
| 26 |
> Portage downloads a tarball of the program's source code, unpacks the source into |
| 27 |
> a temporary working directory (/var/tmp/portage/...) and, assuming the program is |
| 28 |
> written in a compiled language like C or C++, runs `make` [1] before compiling it |
| 29 |
> and copying the compiled executable(s) into the right place on the live filesystem. |
| 30 |
> |
| 31 |
> Using `ebuild /path/to/some.ebuild command` breaks down this process into stages. |
| 32 |
> So you have unpacked it (with `ebuild unpack`), modified the source code and then |
| 33 |
> told emerge to continue the compilation process. |
| 34 |
|
| 35 |
Thank you for your explanation. |
| 36 |
|
| 37 |
>> There was nothing in the output from the uncommented line (/encoding |
| 38 |
>> finds nothing). |
| 39 |
> |
| 40 |
> In fact, I have just checked `man ebuild` and you need to run |
| 41 |
> `sudo ebuild /usr/portage/app-misc/gtypist/gtypist-2.9.5.ebuild merge` |
| 42 |
> to complete the emerge process (by merging the changed package into |
| 43 |
> the live filesystem). I apologise - that is the command I should have told |
| 44 |
> you to finish with in the first place. |
| 45 |
|
| 46 |
I have unpacked the ebuild, uncommented the line |
| 47 |
printf("encoding is %s, UTF8=%d\n", locale_encoding, isUTF8Locale); |
| 48 |
in the /var/tmp/portage/app-misc/gtypist-2.9.5/work/gtypist-2.9.5/src/gtypist.c |
| 49 |
and merged it with the command you mentioned. |
| 50 |
|
| 51 |
Everything went smooth, except that the screen output contains no word |
| 52 |
"encoding" |
| 53 |
though it should. So, I am still puzzled. |
Archives