On 03/04/2011 01:24 PM, Kristopher Gamrat wrote: I'm sorry for not explaining. Arch builds out of source with a new working copy that is checked out (or svn up) updated by the script. The build script operates in any directory you put the build script in. (the build script is named PKGBUILD in Arch) If there are any patches, they go in the directory with the PKGBUILD. Take for example kdenetworkmanager (what I'm working on now) I just create a directory trinity-app-kdenetworkmanager (it could just a easily be named 'anything') and put the PKGBUILD script in it. Running 'makepkg' then creates a /pkg and /src directory under the directory with the PKGBUILD: trinity-app-kdenetworkmanager - PKGBUILD \-pkg (where the finished files are copied for packaging) \-src (where the svn source gets downloaded -- eg.) \- knetworkmanager \- .svn \- admin \- cmake \- knetworkmanager-0.8 So when I'm talking about deleting the source directory, I'm just talking about deleting my working copy in trinity-app-kdenetworkmanager/src above and pulling a fresh source. In the case of this problem on this one box, I have probably built with the same source 10 times, so I just remove the src directory and copy the directory from my pristine source tree into the working directory/src dir. So I guess you could say that this is building in source in a working copy :) Originally I had started out building out of source using using the full svn tree where the PKGBUILD was place in the tree (i.e. applications/kdenetwork) where makepkg would then create a src for building out of code. However, this doesn't meet the Arch standard of the PKGBUILD script being self-contained and automatically retrieving the source-code for you. So after I got things figured out enough to get things going, I went back and re-wrote the PKGBUILD scripts to be Arch standards compliant :) I'll check this box out again after I'm finished working with knetworkmanager. -- David C. Rankin, J.D.,P.E.