public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new virtual -- virtual/go to fix go build time dependencies
Date: Thu, 2 Mar 2017 14:56:37 +0000	[thread overview]
Message-ID: <20170302145637.51df7c0d@snowblower> (raw)
In-Reply-To: <9049c20c-e5b2-c554-9211-2da7eef055df@gentoo.org>

On Thu, 2 Mar 2017 09:47:35 -0500
Michael Orlitzky <mjo@gentoo.org> wrote:
> On 03/02/2017 09:24 AM, Mike Gilbert wrote:
> >>
> >> In other words, the ":=" only does something special in RDEPEND.
> >> That makes sense when you think of it as meaning "the thing will
> >> break" rather than "I want to do a rebuild." The only reason it's
> >> not an error to put them in DEPEND is because it would annoy
> >> everyone doing DEPEND="${RDEPEND}".  
> > 
> > Portage has interesting behavior for ":=" in DEPEND: it varies
> > depending on your "with-bdeps" setting.
> >   
> 
> This is why we can't have nice things.

Actually you can't have nice things because the labels proposal was
voted down for "being invented by the wrong people".

-- 
Ciaran McCreesh


  reply	other threads:[~2017-03-02 14:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  0:18 [gentoo-dev] new virtual -- virtual/go to fix go build time dependencies William Hubbs
2017-03-02  3:45 ` Mike Gilbert
2017-03-02  3:47 ` [gentoo-dev] " Jonathan Callen
2017-03-02  9:58 ` [gentoo-dev] " Alexis Ballier
2017-03-02 14:03   ` Michael Orlitzky
2017-03-02 14:24     ` Mike Gilbert
2017-03-02 14:47       ` Michael Orlitzky
2017-03-02 14:56         ` Ciaran McCreesh [this message]
2017-03-02 15:14           ` Alexis Ballier
2017-03-02 19:05         ` Zac Medico
2017-03-02 19:24           ` Michael Orlitzky
2017-03-02 21:06             ` Zac Medico
2017-03-02 21:25               ` Michael Orlitzky
2017-03-02 21:30                 ` Ciaran McCreesh
2017-03-02 21:46                   ` Michael Orlitzky
2017-03-02 21:53                     ` Alexis Ballier
2017-03-02 22:36                       ` Michael Orlitzky
2017-03-02 23:11                         ` Alexis Ballier
2017-03-07 22:40                     ` William Hubbs
2017-03-07 23:51                       ` Michael Orlitzky
2017-03-08  0:02                         ` Patrick McLean
2017-03-08  0:13                           ` Michael Orlitzky
2017-03-08  0:38                             ` William Hubbs
2017-03-08  6:27                               ` Zac Medico
2017-03-08 12:44                                 ` Michael Orlitzky
2017-03-08 19:20                                   ` William Hubbs
2017-03-08 19:28                                     ` Zac Medico
2017-03-09  0:49                                     ` Michael Orlitzky
2017-03-09 15:36                                       ` William Hubbs
2017-03-09 16:06                                         ` Michael Orlitzky
2017-03-10  7:53                                           ` Alexis Ballier
2017-03-10 14:44                                           ` Kristian Fiskerstrand
2017-03-08  8:07                       ` Kent Fredric
2017-03-08  8:18                         ` Michał Górny
2017-03-02 21:34               ` Alexis Ballier

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=20170302145637.51df7c0d@snowblower \
    --to=ciaran.mccreesh@googlemail.com \
    --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