[arch-general] Need help understanding meta-PKGBUILDs
David C. Rankin
drankinatty at suddenlinkmail.com
Tue Feb 1 23:41:21 EST 2011
We have made good progress refining the basics for Trinity PKGBUILDs. The
trinity/dependencies PKGBUILDs are working for tqtinterface and arts.
They have been reworked to conform with the kde4 (kde-meta) PKGBUILD
structure. But, I'm having trouble understanding how to 'tie' the meta-PKGBUILDs
together with the actual PKGBUILDs for the individual trinity modules. Here are
the questions I have:
(1) can I have 3-levels of PKGBUILDs?
Example: the trinity directory structure is:
Following the kde4 layout, I was trying to create something like this:
I have the arts and tqtinterface level PKGBUILDs done, but I don't know how
to tie them to the trinity-meta PKGBUILDs above. Looking at the kde4 examples, I
have the following:
pkgdesc=('Meta package for trinity-dependencies')
pkgdesc=('Meta package for dependencies-tqtinterface')
pkgdesc=('Meta package for dependencies-arts')
What I don't understand is how does calling the trinity level PKGBUILD
invoke the trinity/dependencies level PKGBUILD and so on....
(2) I googled using arch meta pkgbuild, but I haven't come up with a good
reference. Does anyone have a good link or reference?
https://wiki.archlinux.org/index.php/Makepkg don't really explain it.
(3) Lastly, if anybody has interest, please look over the PKGBUILDs and let me
know where I'm doing something stupid. I have done quite a bit of reading trying
to digest PKGBUILDs and how to apply them to a large project like Trinity. I
don't claim to be an expert on them, so I know there are places where they need
David C. Rankin, J.D.,P.E.
More information about the arch-general