X-Original-To: alpine-user@lists.alpinelinux.org Received: from mail-yb0-f195.google.com (mail-yb0-f195.google.com [209.85.213.195]) by lists.alpinelinux.org (Postfix) with ESMTP id D96BA5C5169 for ; Fri, 22 Jun 2018 04:28:21 +0000 (GMT) Received: by mail-yb0-f195.google.com with SMTP id e84-v6so2076280ybb.0 for ; Thu, 21 Jun 2018 21:28:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nEZn8qCSUKwWqeO9Gt0p97B4H3AI44wdsVoZgI71he4=; b=RVH40U+Rj7QZP9R+r/Tv6I1L3FjIm7N937ysVON+2F/cV3n1thNq45vV4dkubToQFX KBjV3k3rmkKwYGms+oILFeIeDZlBEAiraT5yD2EYzgM1q/fkwMcimhsWydT9lK2dkqBC le/FTg0QskLZMu9HOFek/crcpEhyMVAzyTP7ObYQIsaUbl1A0CRWmc+GZdFfG6i9V/Wk vHSY4M1CuwQ9+DbpXQyNgvLOWIQYo8K9n2UF76DpqC4xO/ts7EKlo0ZxD7B7K/sXfeTD FapZv4umsnYN5cYmwd99v2tlnEee3fhT4728BRcCxqHid31C3GMsw8JpGXg6Q6sNkO2b 0QTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nEZn8qCSUKwWqeO9Gt0p97B4H3AI44wdsVoZgI71he4=; b=i8bwnk4lLR6hcBwG2GEBUXJST6Q6QybT7Bh2So5xhDPFyMOvipc29Jv/cCJlvbwxIt BmPoMA4Q9rxmglnN1Uv/UokD6Zbec/ACXKQt1vHPL7cP/zyMLDUXjvEW1dPa2aii94aK MIf0aHe6pUesl5yTeBfDcpYHqU8mTIQs+u7yw4hZn/60RmhAj5E5drvWyMu/SDRjmNlA n9uz7WGqfOCLCEJYT5U+QQum9rJo4XH/cfFdFOhC1V0bGo/dFazVEEm3BaWdmJh9fVI7 8GX3tDPZ0CyMpyslVXKzTqqgbOXOfn27iDyj4fKHYLJw8yEKD2Luv91Y9YL947ktpo54 Cg3g== X-Gm-Message-State: APt69E0ZD2SDQsGRGu7sXAU19W+4Ygf8iH+XjDuf1snQvaHEzKGv4yMW W/fufB+7pbYiBRli8znlGzkq3MrVTzZ3Y3FpcGg= X-Google-Smtp-Source: ADUXVKJ+oqaOtMXAgSCzQh3ajdaMyxAsKKJ6W2SLlvxwcUepAEjADlg8khnXBj2fM7j5qfPumoODKXRPolO/ab8TbiE= X-Received: by 2002:a25:dacc:: with SMTP id n195-v6mr454ybf.471.1529641700676; Thu, 21 Jun 2018 21:28:20 -0700 (PDT) X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 2002:a25:143:0:0:0:0:0 with HTTP; Thu, 21 Jun 2018 21:28:20 -0700 (PDT) In-Reply-To: <293f7579-94b1-4318-659d-53b17fcf36ed@h6g.de> References: <293f7579-94b1-4318-659d-53b17fcf36ed@h6g.de> From: Dan Cook Date: Thu, 21 Jun 2018 21:28:20 -0700 Message-ID: Subject: Re: [alpine-user] How do I creating a binary only package? To: Paul Zillmann Cc: alpine-user@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="00000000000033db25056f337666" --00000000000033db25056f337666 Content-Type: text/plain; charset="UTF-8" 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): /etc/init.d/foo /opt/foo/bin/say_hi /opt/foo/etc/hello_msgs.db 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: /home/dan/projects/foo/dist/etc/init.d/foo /home/dan/projects/foo/dist/opt/foo/bin/say_hi /home/dan/projects/foo/dist/opt/foo/etc/hello_msgs.db >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: APKBUILD foo.XXXX scripts (like pre, post, etc). What I am stuck on is the contents of the APKBUILD. Let me try this very simple application and see if I can get a installable pkg. Any hints/tips would be helpful. Thanks, Dan On Thu, Jun 21, 2018 at 11:18 AM, Paul Zillmann 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. > > Paul > > > 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? >> >> Thanks, >> Dan >> > > > --- > Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org > Help: alpine-user+help@lists.alpinelinux.org > --- > > --00000000000033db25056f337666 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Paul.=C2=A0 I will try it.=C2=A0 I have a question = regarding the directory structure.=C2=A0 I am familiar with rpm and deb pac= kaging where the directory structure is exactly as that on install target m= achine (the one installing the pkg).=C2=A0 When you say the package functio= n copies to the final destination - which final destination - the destinati= on from the packaging perspective or the install.=C2=A0 I assume it is the = package.
So for example, say I have an app called foo with the followin= g directory layout on the disk (after install):
=C2=A0 /etc/init.= d/foo
=C2=A0 /opt/foo/bin/say_hi
=C2=A0 /opt/foo/etc/he= llo_msgs.db

After I compile my code the binaries a= nd data directory tree is mirrored under:=C2=A0 /home/dan/projects/foo/dist= (very similar to rpm/deb pkg format)
So just for completeness:
=C2=A0 =C2=A0/home/dan/projects/foo/dist/etc/init.d= /foo=C2=A0=C2=A0
=C2=A0 =C2=A0/home/dan/pro= jects/foo/dist/opt/foo/bin/say_hi
=C2=A0 =C2=A0<= /span>/home/dan/projects/foo/dist/opt/foo/etc/hello_msgs.db

From the examples I have seen I would create a directo= ry called pkg under the /home/dan/projects/foo directory and add the follow= ing files:
=C2=A0 APKBUILD
=C2=A0 fo= o.XXXX scripts (like pre, post, etc).

<= div>What I am stuck on is the contents of the APKBUILD.
=
Let me try this very simple application and see if I can get= a installable pkg.=C2=A0 Any hints/tips would be helpful.

Thanks,=C2=A0
Dan
=C2=A0


On Thu, Jun 21, 2018 at 11:18 AM, Paul Zillmann <p.zillmann@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.

Paul


Am 21.06.2018 um 08:11 schrieb Dan Cook:
Hoping to get some pointers on how to create a binary only pkg.=C2=A0 I hav= e the binaries already compiled on Alpine and all I need to do is package t= hem up.=C2=A0 I don't want abuild to compile for me.=C2=A0 I already ha= ve the directory structure layout in a separate directory ready to go.=C2= =A0 All I need is to package up the directory structure and create a instal= lable package. All the docs reference abuild doing the compiling/etc.=C2=A0= Do I use abuild for this or some other tool?

Thanks,
Dan


---
Unsubscribe:=C2=A0 alpine-user+unsubscribe@lists.alpinelinux= .org
Help:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alpine-user+help@lists.alpinelinux.org
---


--00000000000033db25056f337666-- --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---