Arch-general

Download

arch-general@lists.archlinux.org

February 2011

97 participants
92 discussions

[arch-general] PKGBUILD - howto handle 'src' when svn source is already in PKGBUILD dir?
by David C. Rankin 01 Feb '11

01 Feb '11

Guys, I'm trying to figure out the best way to create a set of PKGBUILDs for the Trinity svn tree. I already have the svn source on my computer. I can check for the latest version or svn up each module and I can have makepkg 'redownload' the latest rev in $startdir/src, but HOW do I setup the PKGBUILD to just use what is already in the svn tree? Example: arts I have the following in the dependencies/arts directory: .svn admin artsc cmake doc examples flow gmcop libltdl mcop mcop_mt mcopidl qtmcop soundserver tests x11 CMakeLists.txt COPYING COPYING.LIB INSTALL Makefile.am.in Makefile.cvs arts.lsm arts.pc.cmake config.h.cmake configure.in.bot configure.in.in Since I already have the source, I don't want to create a new $startdir/src/arts under the dependencies/arts directory by simply calling makepkg in that directory. (unless there is some out-of-source trick using links or the like) I'd like to find a way to just do a PKGBUILD to use the source in the current directory and then create the pkg directory in another location. Is there a standard way of handling PKGBUILDs for each module in a large tree that can do this? It's almost like I want to use --noextract while creating a link from src -> ./, but that just seems screwy. Anybody got a trick for doing this? -- David C. Rankin, J.D.,P.E.

2 4

[arch-general] wiki page for Building Trinity on Arch - You want it here or on the trinity site?
by David C. Rankin 01 Feb '11

01 Feb '11

Guys, As I work through building the pkgbuilds for Trinity on Arch, I have been keeping notes, etc. on what has to take place. I will put that information up on a wiki. My question to the Arch devs is "do you want it here on the Arch wiki, or do you want it over on the Trinity wiki?" It doesn't matter to me. It makes more sense to have it here, but there has been so much rancor over 'kde3 is dead' that I don't want to go to the effort here if somebody is just going to nix it. For the interested, Trinity is no longer kde3. It is currently actively developed, and is moving to cmake and qt4. There are current builds for Debian, Ubuntu and Slackware being maintained. My goal is to create a set of pkgbuilds for Arch (which will obviously take a bit of time). But if I can get them working from the svn tree, it should be a great resource for Arch. So what say the powers that be? Do the wiki page here or at Trinity? -- David C. Rankin, J.D.,P.E.

7 11