public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: USE flags in virtuals, to allow a specific provider to be determined
Date: Sat, 26 Jul 2014 10:28:17 +0200	[thread overview]
Message-ID: <1406363297.20388.29.camel@gentoo.org> (raw)
In-Reply-To: <20140725211828.11d89a37@googlemail.com>

El vie, 25-07-2014 a las 21:18 +0100, Ciaran McCreesh escribió:
> On Fri, 25 Jul 2014 22:12:53 +0200
> Pacho Ramos <pacho@gentoo.org> wrote:
> > Ah, ok, I was wondering why REQUIRED_USE was implemented then :/, I
> > guess it was for simplifying ebuilds?
> 
> It was a historical mistake: originally we were going to use
> pkg_pretend for this. But claims were made that this would break some
> mythical auto-building systems, and that something machine-readable was
> needed. Unfortunately the Council bought this, and put through
> REQUIRED_USE without a reference implementation.
> 
> Needless to say, the end result is something that isn't human-readable,
> and isn't used by any mythical auto-building systems.
> 
> (Incidentally, Exherbo has a both human- and machine-readable
> implementation, which *is* used by an auto-building system, but the
> syntax won't meet Gentoo approval...)
> 

Maybe REQUIRED_USE could allow us to set an error message for each line
to allow us to instruct PMs about what message should they who to the
users :/ (it would show our message that should be more clear, a bit
like we are able to do with "die 'message'")



  reply	other threads:[~2014-07-26  8:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 18:49 [gentoo-dev] RFC: USE flags in virtuals, to allow a specific provider to be determined Ian Stakenvicius
2014-07-25 19:04 ` Luis Ressel
2014-07-25 19:23   ` Ian Stakenvicius
2014-07-25 19:44     ` Luis Ressel
2014-07-25 19:46       ` Ciaran McCreesh
2014-07-25 19:49         ` Ian Stakenvicius
2014-07-25 19:51         ` Pacho Ramos
2014-07-25 19:54           ` Ian Stakenvicius
2014-07-25 20:12             ` Pacho Ramos
2014-07-25 20:18               ` Ciaran McCreesh
2014-07-26  8:28                 ` Pacho Ramos [this message]
2014-07-25 21:13               ` Ian Stakenvicius
2014-07-25 21:25                 ` Ciaran McCreesh
2014-07-25 21:23             ` William Hubbs
2014-07-25 21:25               ` Ciaran McCreesh
2014-07-25 21:46                 ` William Hubbs
2014-07-25 21:50                   ` Ciaran McCreesh
2014-07-26 17:45               ` [gentoo-dev] " Jonathan Callen
2014-07-27 15:38                 ` William Hubbs
2014-07-25 20:41 ` [gentoo-dev] " Michał Górny
2014-07-25 21:09   ` Ian Stakenvicius
2014-07-26  7:17     ` justin
2014-07-26  8:05 ` [gentoo-dev] " Duncan
2014-07-26  8:30   ` Pacho Ramos
2014-07-26  8:53   ` Michał Górny
2014-07-26  9:01     ` Duncan
2014-07-26 12:46     ` Ciaran McCreesh
2014-07-26  8:58   ` Duncan
2014-07-26 13:31   ` Ian Stakenvicius
2014-07-26 14:40 ` [gentoo-dev] " Manuel Rüger
2014-07-27 17:11   ` Peter Stuge
2014-07-28 14:20   ` Ian Stakenvicius
2014-07-28 14:42     ` Michał Górny
2014-07-28 15:11       ` Ian Stakenvicius
2014-07-28 11:21 ` Michał Górny
2014-07-28 17:02   ` Ian Stakenvicius
2014-07-29  4:23     ` James Potts
2014-07-29 11:06       ` Ciaran McCreesh
2014-07-29  4:51     ` Michał Górny

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=1406363297.20388.29.camel@gentoo.org \
    --to=pacho@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