| 1 |
Stroller <stroller@××××××××××××××××××.uk> writes: |
| 2 |
|
| 3 |
> But if you consider it a hassle, just mask the buggy version of |
| 4 |
> procmail & forget about the problem. |
| 5 |
|
| 6 |
Thanks... I thought of something like that but then noticed there's only |
| 7 |
one version available in portage. |
| 8 |
|
| 9 |
At that point I downloaded the previous version *21* tar ball and |
| 10 |
attempted to build it just manually but hit the same getline problem. |
| 11 |
(this was outside emerge) |
| 12 |
|
| 13 |
The next version back behind 21 is quite old. |
| 14 |
(I then built an installed version 22* by hand using the sed tools |
| 15 |
... more below about that) |
| 16 |
|
| 17 |
But can't I do something when the emerge breaks and tells me where the |
| 18 |
sources are in /var/tmp... can't I go there and finish the build |
| 19 |
somehow? First the sed run, then ebuild (I know those ebuild |
| 20 |
commands) and have the finished product installed with emerge? |
| 21 |
|
| 22 |
And similarly with CVS. I remember there being some way I could tell |
| 23 |
emerge to let me set a ./configure flag by hand... then finish the |
| 24 |
install (with emerge). May have been some flag set right at the |
| 25 |
emerge cmd like: |
| 26 |
|
| 27 |
# SOMEFLAG=something emerge -v cvs |
| 28 |
|
| 29 |
Just for information... I have built procmail *22* by hand using the |
| 30 |
afore mentioned sed command then symlinked /usr/local/bin/procmail to |
| 31 |
/usr/bin/procmail, where sendmail expects it to be, and so am able to |
| 32 |
run it fine and get mail working. So not really a big problem... just |
| 33 |
seems there'd be a fairly easy way to get this done with emerge short |
| 34 |
of going the personal overlay route. |
| 35 |
|
| 36 |
To me... the personal overlay just does not fall under `fairly easy'. |
Archives