public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
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 22:34:37 +0100	[thread overview]
Message-ID: <20170302223437.20b90cbd@gentoo.org> (raw)
In-Reply-To: <39a8f38d-86ac-fd4a-7397-e8db6acc4a60@gentoo.org>

On Thu, 2 Mar 2017 13:06:45 -0800
Zac Medico <zmedico@gentoo.org> wrote:

> On 03/02/2017 11:24 AM, Michael Orlitzky wrote:
> > On 03/02/2017 02:05 PM, Zac Medico wrote:  
> >>>
> >>> This is why we can't have nice things.  
> >>
> >> For those that are interested, I'm planning to to make --with-bdeps
> >> automatically enabled when possible:
> >>  
> > 
> > 
> > I agree with this ^ but I don't think portage should rebuild for
> > DEPEND at all. It creates one more dangerous "it works in portage!"
> > situation that will plague users of other package managers.
> > 
> > (I'm not saying it couldn't be useful, but it should go in the next
> > EAPI if we're gonna do it.)  
> 
> PMS doesn't specify when rebuilds are supposed to be triggered. You
> can consider the rebuilds as a means to satisfy the dependencies.
> Saying that the package manager should not make an effort to satisfy
> dependencies would be silly.


And then have a nice ref. implementation for next EAPI.


Having barely tested (*) features set in stone at each EAPI bump is even
more dangerous than the "it works in portage!" situations IMHO.


(*) I'm not saying features are not tested, but those that have
been thrown at users for years are much more mature than the
brand new ones in comparison.


      parent reply	other threads:[~2017-03-02 21:34 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
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 [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=20170302223437.20b90cbd@gentoo.org \
    --to=aballier@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