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