Arch tde-packaging was [Re: [trinity-devel] Any reason NOT to use libjpeg-turbo instead of libjpeg?]

On 02/21/2012 03:39 PM, Calvin Morrison wrote: Calvin, I am preparing pkgbuild scripts that can be used to pull and build directly from git. Do you have any preference on how you want to layout the arch tde-packaging repo to distinguish this? Currently the scripts build from tarballs made from git and some include path references to dependencies/tqtinterface, etc.. instead of just tqtinterface. I have been cleaning that up as I go along as well as cleaning up the url="pearsoncomputing..." information. Eg: url="http://scm.trinitydesktop.org/scm/git/qt3" Currently the git repository has: tde-packaging/ tde-packaging/arch/ tde-packaging/arch/3.5.13/ tde-packaging/arch/3.5.13_broken/ tde-packaging/arch/extras/ I was thinking about putting the sources that use git in: tde-packaging/arch/git What do you think? Also, how do you want to handle standardizing the pkgbuild path reference information? When I create tarballs, I only keep the needed path information for the files in the tarball. Eg: qt3/ and not dependencies/qt3 Obviously, I cannot update the existing files in 3.5.13 with anything I've done as a result. I was hoping we could figure out what we want to do for Arch and standardize this. I could modify the file that creates the tarballs to include the extra directory information, but that requires that every PKGBUILD have that information hardcoded into it: Eg: cd ${srcdir}/dependencies/${pkgname} instead of just the standard cd ${srcdir}/${pkgname} I think it makes sense to standardize the tarballs in a way that we don't have to worry about custom paths in the PKGBUILD files. What do you think? -- David C. Rankin, J.D.,P.E.