On Monday 03 Nov 2008, Alex Samad wrote: > On Mon, Nov 03, 2008 at 10:19:17AM -0500, Lennart Sorensen wrote: > > On Mon, Nov 03, 2008 at 02:50:48PM +0000, A J Stiles wrote: > > > The bug is in vuescan, if it won't build cleanly from source on a > > > 64-bit system. > > > > It also appears to be proprietary software, so no way to fix that. > > I am a licensed user of the application and the author has been > receptive to feedback previously. > > What would you suggest would be the most constructive way of > *suggesting* to fix the problem.
Ask for the Source Code! After all, you're paying good money for the software. Would you buy a cake without a list of ingredients on the packaging? Absence of Source Code does **nothing** to prevent unauthorised copying, otherwise there wouldn't be so many pirate copies of Windows and Office out there. It does, however, piss off honest users like you -- in more ways than just making them feel that the vendor expects them to be acting dishonestly from the word "go". > So far I have read its a problem with gtk and the other is to test if it > does a clean compile in 64b. If software that was compiled on one machine runs on another machine, then that is just a happy accident. The Proper Way is, and always has been, to compile it on your own machine. The second best way is to have your own machine set up exactly the same as the one on which the software was originally compiled. You can no more expect a package originally compiled for Ubuntu to run on Mandriva than you can expect a map of the route from your kitchen to your bathroom to be valid in someone else's house. Horrendous bodges (such as installing 32-bit libraries on a 64-bit system) are just waiting to come and bite you in the backside. -- AJS delta echo bravo six four at earthshod dot co dot uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
