1 |
I'm really sorry to keep beating on this portage stuff and I guess I |
2 |
must be something of a dimwit since I find just about anything to do |
3 |
with portage and emerge that is outside `emerge -flags whatever' |
4 |
to be really hard to catch on to, even though (and shouldn't admit |
5 |
this) I've been running gentoo for at least 5 yrs and probably more. |
6 |
|
7 |
I read up on the parts I need at times when I run into trouble and get |
8 |
much coaching and pointers here. But then in a few mnths, with no |
9 |
problems I've forgotten the vast bulk of whatever I picked up. And I |
10 |
mean even when I've made notes... |
11 |
|
12 |
Anyway cutting to the chase: |
13 |
|
14 |
I want to do some manual manipulation to a failing emerge of procmail. |
15 |
|
16 |
emerge -v procmail |
17 |
(details here were posted elsewhere but involves somekind missnaming |
18 |
of getline in the ebuild) |
19 |
|
20 |
It fails but has a simple enough fix. It needs to have a sed exchange |
21 |
take place in the unpacked source. |
22 |
|
23 |
Running `sed -i -e 's/getline/get_line/g' src/*.c src/*.h' |
24 |
In top level of the upacked source will allow it to compile fine. |
25 |
So once all instances of getline are changed to get_line... it works. |
26 |
|
27 |
Now how do I go about doing that right during the emerge? |
28 |
|
29 |
For something like this it seems way overkill to have a separate |
30 |
custom /usr/local/portage where I build my own. Especially since I |
31 |
find that whole process difficult and way overkill for this problem. |
32 |
|
33 |
Further its something that will almost certainly be fixed soon and |
34 |
won't be something I have to attend to again. |
35 |
|
36 |
I'm pretty sure there is some way to introduce custom action during |
37 |
emerge and remember doing something like that before to fix cvs so |
38 |
root could commit. It envolved either a ./configure or make flag that |
39 |
portage didn't employ... somehow, with coaching here... I was able to |
40 |
introduce a non-default flag. |
41 |
|
42 |
Isn't there a simple way to introduce the sed run in procmail sources |
43 |
during emerge? |
44 |
|
45 |
Oh, and to fix cvs again too... with this new install I've started from |
46 |
scratch after nursing one original install and upating over yrs. |