greets,
]]>....this way you will not break the AL standard.
I agree when it requires to upload the package to AL's incoming archive with filelist and PKGBUILD for checking. My suggestion is for personal use or to test the package.
]]>First, extract the program.. be sure to use a non-standar prefix e.g:
tar zxpvf mybinary.tar.gz -C /opt/mybinary
check inside /opt/mybinary for the directory tree (usr/bin usr/share .. and so on)
once you've checked the directory tree you can safely pack it again or use the same package as source.
cd /opt/mybinary
tar c usr | gzip -9 > mybinary-version.tar.gz
edit your PKGBUILD and remove configure, make and make install
thats all,
now makepkg will extract it under the prefix ./pkg/ and generate .PKGINFO and filelist and the AL pkg itself.
is easy to undestand that you must be SURE that the directory tree is correct, this way you will not break the AL standars.
good luck,
]]>- write your PKGBUILD as usual and as source=() choose the binary url
- how your build() should look like is depending on the tar.gz content, in general i would first make the necessary dirs in $startdir/pkg ( like usr/bin etc... ) and then cp the files from $startdir/src into the right $startdir/pkg directory as u need it.
(it will maybe take some hand-work but normally this is not that hard)
- then build it with makepkg and install with pacman -A
greetz dariball
]]>