TB0ne |
02-08-2015 10:33 AM |
Quote:
Originally Posted by veerain
(Post 5313591)
There is a difference between a release tarball and a git tarball.
|
No, there STILL isn't, and you're STILL WRONG.
Quote:
Ok the release tarball has gitcompile and it invokes automake/autoconf scripts. But read the INSTALL file. It supports the simple ./configure && make install.
|
...and the EXACT SAME FILES are present in a tarball...so what's your point?
Quote:
And git clone doesn't has Makefile nor configure file only configure.ac and makefile.am. So you would need automake/autoconf macros of all programs that alsa-utils needs for creating configure and makefile.in.
In contrast consider a release tarball it has makefile.in and configure. Run configure with your required options and it produces working Makefile. If you don't want ld10k1 you can just give disable option to configue script.
|
AGAIN, the "git clone" GIVES YOU EXACTLY WHATEVER THE DEVELOPER WANTS TO GIVE YOU. Downloading a tarball does the EXACT same thing...if there's a configure file, it's there in both versions.
The ONLY difference (MAYBE), is if you checkout a different version of the code from GIT, versus tar. You obviously haven't done a git checkout/clone of that, and compared it to the tarball. Because if you had, you'd notice THEY ARE IDENTICAL.
|