From: "Stefan Mühlinghaus" <"master..."@googlemail.com>
To: voidlinux@googlegroups.com
Subject: Re: Few packaging questions
Date: Thu, 22 Jan 2015 15:21:11 -0800 (PST) [thread overview]
Message-ID: <5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com> (raw)
In-Reply-To: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1114 bytes --]
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 :)
[-- Attachment #1.2: Type: text/html, Size: 1191 bytes --]
next prev parent reply other threads:[~2015-01-22 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 20:51 Logen Kain
2015-01-22 23:21 ` Stefan Mühlinghaus [this message]
2015-01-23 3:29 ` Logen Kain
2015-02-02 19:09 ` Logen Kain
2015-01-23 9:13 ` Stefan Mühlinghaus
2015-02-02 19:05 ` Logen Kain
[not found] ` <CABLHwtef9mKadZZFR+06yNZhuOE8YS_Z_3FHE=xgZ9FUoX409Q@mail.gmail.com>
2015-02-02 19:14 ` Fwd: " Juan Romero Pardines
[not found] ` <CABLHwtfWdKPsexjP_p4oscok4US_y8gXWym1qGQ6uf7q7+COxw@mail.gmail.com>
2015-02-02 19:14 ` Juan Romero Pardines
2015-02-02 19:51 ` Logen Kain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com \
--to="master..."@googlemail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).