From: Logen Kain <walach.o...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Few packaging questions
Date: Mon, 2 Feb 2015 11:09:37 -0800 (PST) [thread overview]
Message-ID: <d3d9d3ca-0375-44f1-87dc-2a2b600ae796@googlegroups.com> (raw)
In-Reply-To: <5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1080 bytes --]
>
>
> - *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 just realized I never clarified myself here, my bad.
The way I look at it:
- *hostmakedepends: *Depends that are not architecture specific.
- *makedepends:* Depends that *are* architecture specific. - So I check
if 32-bit packages exist. If they do, I know it's architecture specific.
- *depends: *Same as what you said, which actually helped clarify it a
bit for me.
[-- Attachment #1.2: Type: text/html, Size: 1313 bytes --]
next prev parent reply other threads:[~2015-02-02 19:09 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
2015-01-23 3:29 ` Logen Kain
2015-02-02 19:09 ` Logen Kain [this message]
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=d3d9d3ca-0375-44f1-87dc-2a2b600ae796@googlegroups.com \
--to="walach.o..."@gmail.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).