How to make an AL package from binary files? The folders and files are compressed into one tarball (hwd-0.1.tar.gz) on /home/rasat. Do I use PKGBUILD file? If so, what's the script..... the source and build ()?
The main point is to install and also be able to remove with pacman.
so would do it like this :
- 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
maybe I have a perfect signature _someday_
I found an easier way by checking the scripts of /usr/bin/makepkg. Also I took a look what's the difference between a standard tar.gz tarball and pkg.tar.gz pacman is using. In the root of pkg.tar.gz is .PKGINFO file (hidden file). Depending on the package, this is the info:
# Generated by makepkg 2.4.1
# Sat Apr 19 23:57:36 UTC 2003
pkgname = test
pkgver = 0.1-1
pkgdesc = Test packages
builddate = Sat Apr 19 23:57:36 2003
packager = Arch Linux (http://www.archlinux.org)
size = 4096
How to create an AL package:
1. make one folder (e.g. /test-folder) and copy all folders & files you want to include in the package.
2. with editor make one .PKGINFO file and save it in the folder.
3. run in same folder:
# tar czvf test-0.1-1.pkg.tar.gz .PKGINFO folder1 folder2 file1 file2 file3
i think the better way is to use the standar PKGBUILD and the makepkg command.
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.
tar c usr | gzip -9 > mybinary-version.tar.gz
edit your PKGBUILD and remove configure, make and make install
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.
GNU/Linux: Share & Enjoy!
....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.
you're right, your way is faster but please if somebody wants to upload some pkg to incoming do it the AL way.
GNU/Linux: Share & Enjoy!