Randy McMurchy wrote: > DJ Lucas wrote these words on 03/24/08 01:00 CST: > >> Again, I believe the problem is GMime. > > I'll look at what it would take to patch/sed GMime so that this > borked uudecode program doesn't get installed. But I suppose I > need to check that there's not an updated version of GMime > available first.
If not, then don't omit the installation of them. They probably work fine with the same version of the uuencode and uudecode. Assuming that they are functionally the same (command line args and what not) they should be optionally installed if existing programs aren't found. Really, uuencode and uudecode should be fixed upstream in GMime, but for BerkelyDB, I think we should set uudecode="no" in all cases to avoid breaking GMime. What does that cost us? About 20-30 seconds on a relatively fast machine? BTW, please credit 'Alessandro Alocci' for any related fix. > > Whatever, it should be simple to fix. Knowing what the issue is > means we have 99.9% of the problem fixed. > Thank you for doing all the testing on this. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
