Another fine example of MythTV developers going against the grain :) Come on, adopt autoconf, and a proper automated make script. I remember Isaac once saying he thought autoconf was crap, but I've yet to understand how it is. Furthermore, why is it almost all open source projects use it and it isn't alright to use it for MythTV? I would think the advantages outweigh any possible disadvantages.
Why wouldn't we want dependency library detection, header checks, and automatic system optimization based on probing the system. I still never saw the advantage to having to manually choose by #defines. Kevin Kevin Elliott [EMAIL PROTECTED] http://www.kevinelliott.net/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hillis Sent: Tuesday, January 25, 2005 7:24 PM To: Development of mythtv Subject: Re: [mythtv] CVS Gentoo ebuild Jeremiah Morris wrote: > >> However, it is the only way to build Myth in parallel, which is what >> my original post said. > > Ah, I see, you're trading our user support time (and patience), and > the user's time (in dealing with a broken ebuild), for compilation > time (when it's not broken, that is). Thanks for clearing that up. Never mind. You're missing my point entirely. My point was that many, many other packages build fine in parallel. But never mind - I really don't feel like continuing an argument that isn't going anywhere. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.4 - Release Date: 25/01/2005 _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
