On Thu, Feb 16, 2012 at 2:46 PM, Calvin Morrison <mutantturkey@...> wrote: > On 16 February 2012 08:39, David C. Rankin > <drankinatty@...> wrote: >> Guys, >> >> Working with the current tarballs compared with those created from the git >> tree I have run into a difference in path information included in the existing >> tarballs instead of those created from a local copy of the git tree. The >> existing tarballs referenced in the PKGBUILD scripts contain the dependencies >> path information i.e.: >> >> dependencies/tqtinterface/ >> dependencies/tqtinterface/TODO >> dependencies/tqtinterface/ConfigureChecks.cmake >> dependencies/tqtinterface/COPYING >> dependencies/tqtinterface/CMakeLists.txt >> dependencies/tqtinterface/configure.in.mid >> dependencies/tqtinterface/qtinterface/ >> dependencies/tqtinterface/qtinterface/tqlcdnum.h >> dependencies/tqtinterface/qtinterface/parser2.sh >> >> While those I create from the git tree simply contain e.g.: >> >> tqtinterface/CMakeLists.txt >> tqtinterface/configure.in.bot >> tqtinterface/AUTHORS >> tqtinterface/admin/ >> tqtinterface/configure.in.mid >> >> Is prefixing the files in the tarball with the entire directory path below >> 'main/' going to be the standard? In the past, I have always excluded the module >> prefix (applications, common, dependencies, libraries, ...). >> >> Either way will work, but from a PKGBUILD standpoint, we need to make sure >> there is a standard. What is the consensus? >> >> >> -- >> David C. Rankin, J.D.,P.E. > > We have been working solely with the 3.5.13 tarballs. Now that git has > settled we also going to work on git builds. > > Calvin > I'd rather use tarballs for stable builds rather than git. Anyway, the pkgbuilds for r13 aren't exactly finished, they still need some polishing.