From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.236.47.137 with SMTP id t9mr3139278yhb.43.1421968872310; Thu, 22 Jan 2015 15:21:12 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.21.175 with SMTP id 44ls825512qgl.99.gmail; Thu, 22 Jan 2015 15:21:12 -0800 (PST) X-Received: by 10.140.31.134 with SMTP id f6mr39820qgf.33.1421968872124; Thu, 22 Jan 2015 15:21:12 -0800 (PST) Date: Thu, 22 Jan 2015 15:21:11 -0800 (PST) From: =?UTF-8?Q?Stefan_M=C3=BChlinghaus?= To: voidlinux@googlegroups.com Message-Id: <5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com> In-Reply-To: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> Subject: Re: Few packaging questions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_981_1952996705.1421968871828" ------=_Part_981_1952996705.1421968871828 Content-Type: multipart/alternative; boundary="----=_Part_982_1775092243.1421968871833" ------=_Part_982_1775092243.1421968871833 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, a packing howto would be interesting, especially dependency resolution. My current approach is working so far, but I'm wondering if it could not be streamlined. Are there any void-tools that support manual dependency resolution? Also I don't think I understand your reasoning of what to add to which "depends"-variable. Maybe I'm misunderstanding you, but this is how I divide them: - *hostmakedepends:* All the stuff that the building machine needs to be able to run through the building process. Mostly tools, like pkg-config or somesuch. This is needed regardless of which architecture you are building for. - *makedepends:* All stuff that is needed du build the package on the building machine. Usually devel-versions of the required libraries. This is dependant on the architecture you are building for. - *depends:* All the stuff required to run the package on the target system. Not needed at all on the building machine, and dependant on the target architecture. I'm probably stating something obvious here, but there you go :) ------=_Part_982_1775092243.1421968871833 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Yes, a packing howto would be interesting, especially depe= ndency resolution. My current approach is working so far, but I'm wondering= if it could not be streamlined. Are there any void-tools that support manu= al dependency resolution?

Also I don't think I understan= d your reasoning of what to add to which "depends"-variable. Maybe I'm misu= nderstanding you, but this is how I divide them:

<= ul>
  • hostmakedepends: All the stuff that the building machine need= s to be able to run through the building process. Mostly tools, like pkg-co= nfig or somesuch. This is needed regardless of which architecture you are b= uilding for.
  • makedepends: All stuff that is needed du bu= ild the package on the building machine. Usually devel-versions of the requ= ired libraries. This is dependant on the architecture you are building for.=
  • depends: All the stuff required to run the package on t= he target system. Not needed at all on the building machine, and dependant = on the target architecture.

    • I'm prob= ably stating something obvious here, but there you go :)
    ------=_Part_982_1775092243.1421968871833-- ------=_Part_981_1952996705.1421968871828--