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.