public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Paweł Hajdan, Jr." <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] crossdev: installing _host_ build dependencies not automatic?
Date: Sat, 13 May 2017 21:41:54 +0200	[thread overview]
Message-ID: <e451ebc5-2170-b5ef-753e-a711fa29f389@gentoo.org> (raw)
In-Reply-To: <20170503175643.316ff1aa@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1026 bytes --]

On 03/05/2017 17:56, Alexis Ballier wrote:
> From man emerge:
> 
>        --root-deps[=rdeps]
>               If  no argument is given then build-time dependencies of
>        packages for ROOT are installed to ROOT instead of /.  If the
>        rdeps argument is given then discard all build-time dependencies
>        of packages for ROOT.  This option is only meaningful when used
>        together with ROOT and it should not be enabled under normal
>        circumstances!

Ah, I didn't know about that. Thanks!

>               Does not affect EAPIs that support HDEPEND.  Experimental
>               EAPI 5-hdepend provides HDEPEND as a new means to adjust
>               installation into "/" and ROOT.  If ebuilds using EAPIs
>               which do not support HDEPEND are built  in  the same
>               emerge run as those using EAPIs which do support HDEPEND,
>               this option affects only the former.

Curious - what's the status of HDEPEND for the main tree?

Paweł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

      parent reply	other threads:[~2017-05-13 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 10:05 [gentoo-dev] crossdev: installing _host_ build dependencies not automatic? Paweł Hajdan, Jr.
2017-05-03 15:56 ` Alexis Ballier
2017-05-03 21:47   ` James Le Cuirot
2017-05-04  8:21     ` Alexis Ballier
2017-05-13 19:41   ` Paweł Hajdan, Jr. [this message]

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=e451ebc5-2170-b5ef-753e-a711fa29f389@gentoo.org \
    --to=phajdan.jr@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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