On 02/06/2011 10:49 AM, Tavian Barnes wrote:
On 4 February 2011 23:02, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
How do I tell makechrootpkg to use the files in the same directory as the PKGBUILD? In the PKGBUILD I simply have:
Why is the checkout in the same directory as the PKGBUILD? Have a look at /usr/share/pacman/PKGBUILD-svn.proto, and every -svn package in the repos/AUR. The checkout happens into src/trinity (for example), which is copied to src/trinity-build, where the build takes place.
Tavian, thanks for your suggestion. For trinity, the whole svn tree is already on my computer: ~/tbld/trinity ~/tbld/trinity/dependencies ~/tbld/trinity/dependencies/tqtinterface ~/tbld/trinity/dependencies/arts ~/tbld/trinity/kdelibs <snip> I have the PKGBUILDs each trinity module directory (eg. {tqtinterface,arts,kdelibs,etc...} ) So there is no 'svn checkout' performed from within the PKGBUILDs. For example, each directory is similar to the following: 20:35 alchemy:~/tbld/trinity/kdelibs> ls -1 admin arts cmake dcop <snip> CMakeLists.txt <snip> PKGBUILD <snip> From ${srcdir}, cmake is called by: cmake ../ This fails with makechrootpkg because nothing gets copied to the chroot. Is there a way to fix this? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com