> Thanks Paul. I will try it. I have a question regarding the
> directory structure. I am familiar with rpm and deb packaging where
> the directory structure is exactly as that on install target machine
> (the one installing the pkg). When you say the package function
> copies to the final destination - which final destination - the
> destination from the packaging perspective or the install. I assume
> it is the package.
> So for example, say I have an app called foo with the following
> directory layout on the disk (after install):
That is correct. You can download an apk file (e.g.
), rename it to tar.gz and open it up.
The package content is an overlay to the root directory and is alway
applied to the root directory.
> After I compile my code the binaries and data directory tree is
> mirrored under: /home/dan/projects/foo/dist (very similar to rpm/deb
> pkg format)
> So just for completeness:
> From the examples I have seen I would create a directory called pkg
> under the /home/dan/projects/foo directory and add the following files:
> foo.XXXX scripts (like pre, post, etc).
> What I am stuck on is the contents of the APKBUILD.
You have to copy your included files to the pkg folder as well. (cp
~/projects/foo/dist/etc/init.d/foo ~/projects/foo/pkg/foo.initscript etc.pp)
Now you create yourself an APKBUILD file:
# Contributor: Your Name <yourmail_at_example.com>
# Maintainer: Your Name <yourmail_at_example.com>
pkgdesc="Sample for binary distribution"
mkdir -p "$pkgdir"/etc/init.d/ "$pkgdir"/opt/foo/bin/
install -m755 -D "$srcdir"/say_hi "$pkgdir"/opt/foo/bin/say_hi
|| return 1
install -m644 -D "$srcdir"/hello_msgs.db
"$pkgdir"/opt/foo/etc/hello_msgs.db || return 1
install -m644 -D "$srcdir"/foo.initscript
"$pkgdir"/etc/init.d/foo || return 1
Abuild will then add the sha512 checksums to that file and create a package.
> Let me try this very simple application and see if I can get a
> installable pkg. Any hints/tips would be helpful.
> On Thu, Jun 21, 2018 at 11:18 AM, Paul Zillmann <p.zillmann_at_h6g.de
> <mailto:p.zillmann_at_h6g.de>> wrote:
> Hello Dan,
> just create a package with abuild / apkbuild.
> In your APKBUILD file you have to provide a package() function
> which copies your binary data to it's final destination.
> You will have to provide a build() function. Than one can be empty
> (or you return 0) - but it has to be there.
> Am 21.06.2018 um 08:11 schrieb Dan Cook:
> Hoping to get some pointers on how to create a binary only
> pkg. I have the binaries already compiled on Alpine and all I
> need to do is package them up. I don't want abuild to compile
> for me. I already have the directory structure layout in a
> separate directory ready to go. All I need is to package up
> the directory structure and create a installable package. All
> the docs reference abuild doing the compiling/etc. Do I use
> abuild for this or some other tool?
> Unsubscribe: alpine-user+unsubscribe_at_lists.alpinelinux.org
> Help: alpine-user+help_at_lists.alpinelinux.org
Received on Fri Jun 22 2018 - 13:51:22 GMT