public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Guidelines for IUSE defaults
Date: Thu, 2 Feb 2017 11:25:24 -0500	[thread overview]
Message-ID: <68433328-e9a2-03ec-bad7-c81a0d8f442c@gentoo.org> (raw)
In-Reply-To: <CAGfcS_n5VxtJEUMxr60-f6wn+95DgnemuLkO+Pnm+3utPB99Aw@mail.gmail.com>

On 02/02/2017 11:08 AM, Rich Freeman wrote:
> 
> Which is simpler, a minimal profile that sets USE=-* and then lists a
> few exceptions where that breaks in package.use, or an upstream
> defaults profile (which becomes the basis for all the other profiles)
> that has a 5000 line package.use file that specifies the upstream
> defaults for every package in the repository?
> 

It's honestly hard to say. I see your point, but "a few exceptions"
might not be so few. Every IUSE default that

  (1) enables something critical, or
  (2) enables a default choice for a REQUIRED_USE constraint

would need to be added back to the minimal profile. And of course the
reason I started this thread is that those two usages are common. I
clearly had the "minimal base" profile in mind, but the fact that (1)
and (2) are used throughout the tree creates problems for any minimal
profile, even is the base profile is "upstream defaults."

If (base == minimal), then all of the upstream defaults need to be added
to package.use for the upstream-defaults profile. That's bad, but if
(base == upstream-defaults), then the important IUSE defaults need to be
copy/pasted from our ebuilds into the minimal profile. The latter is
more spiritually damning =)



  reply	other threads:[~2017-02-02 16:25 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 14:11 [gentoo-dev] Guidelines for IUSE defaults Michael Orlitzky
2017-02-02 14:56 ` Ian Stakenvicius
2017-02-02 15:49   ` Michael Orlitzky
2017-02-03  8:16     ` [gentoo-dev] " Duncan
2017-02-02 15:06 ` [gentoo-dev] " Kristian Fiskerstrand
2017-02-02 15:11   ` James Le Cuirot
2017-02-02 15:36   ` Michael Orlitzky
2017-02-02 15:51     ` [gentoo-dev] icedtea requiring X libs to build was -> " William L. Thomson Jr.
2017-02-02 15:53       ` Michael Orlitzky
2017-02-02 16:09         ` James Le Cuirot
2017-02-02 16:13           ` Michael Orlitzky
2017-02-02 16:18             ` William L. Thomson Jr.
2017-02-02 16:27               ` Michael Orlitzky
2017-02-02 17:06                 ` William L. Thomson Jr.
2017-02-02 17:18                   ` Michael Orlitzky
2017-02-02 23:07                     ` William L. Thomson Jr.
2017-02-02 16:16         ` William L. Thomson Jr.
2017-02-02 15:52     ` [gentoo-dev] " Rich Freeman
2017-02-02 15:59       ` Michael Orlitzky
2017-02-02 16:08         ` Rich Freeman
2017-02-02 16:25           ` Michael Orlitzky [this message]
2017-02-02 18:01             ` Rich Freeman
2017-02-02 20:35               ` james
2017-02-02 21:05                 ` Rich Freeman
2017-02-02 23:28                   ` james
2017-02-03  0:12                     ` Rich Freeman
2017-02-02 21:40                 ` David Seifert
2017-02-02 23:35                   ` james
2017-02-02 23:41                     ` Ian Stakenvicius
2017-02-03  1:21                       ` Michael Orlitzky
2017-02-03 13:17                         ` Ian Stakenvicius
2017-02-02 23:47                 ` Daniel Campbell
2017-02-03  0:01               ` Gordon Pettey
2017-02-04  0:34                 ` Kent Fredric
2017-02-03  1:40               ` Michael Orlitzky
2017-02-03  2:10                 ` Rich Freeman
2017-02-03  3:14                 ` Patrick McLean
2017-02-03 13:21                   ` Ian Stakenvicius
2017-02-03 13:43                     ` Michael Orlitzky
2017-02-03 15:30                       ` Ian Stakenvicius
2017-02-03 19:37                         ` Michael Orlitzky
2017-02-04  0:59                           ` Ian Stakenvicius
2017-02-04  1:07                             ` Patrick McLean
2017-02-04 14:57                               ` Michael Orlitzky
2017-02-04 17:44                                 ` William L. Thomson Jr.
2017-02-04 18:14                                   ` Kent Fredric
2017-02-04 21:05                                     ` William L. Thomson Jr.
2017-02-04 22:13                                       ` Kent Fredric
2017-02-09  2:46                                       ` Daniel Campbell
2017-02-03 18:33                       ` Patrick McLean
2017-02-03 19:53                         ` Michael Orlitzky
2017-02-03 22:09                           ` William L. Thomson Jr.
2017-02-09 20:18                             ` Daniel Campbell
2017-02-09 20:25                               ` Ben Kohler
2017-02-09 20:41                                 ` Daniel Campbell
2017-02-09 20:59                                   ` Michael Orlitzky
2017-02-09 21:25                                     ` Daniel Campbell
2017-02-03  6:12               ` Walter Dnes
2017-02-03 17:39                 ` james
2017-02-03 19:01                   ` james
2017-02-02 15:52     ` James Le Cuirot
2017-02-02 21:17     ` Dirkjan Ochtman
2017-02-02 15:57   ` james
2017-02-02 17:23 ` Walter Dnes
2017-02-02 17:28   ` Michael Orlitzky
2017-02-03  2:00 ` Sam Jorna
2017-02-03  2:06   ` Michael Orlitzky
2017-02-03  2:22     ` Sam Jorna
2017-02-03  2:26       ` Michael Orlitzky
2017-02-03  2:34         ` Sam Jorna
2017-02-03  2:31     ` Rich Freeman
2017-02-03  2:55       ` Michael Orlitzky
2017-02-03  3:16     ` Patrick McLean
2017-02-03  3:37       ` Michael Orlitzky
2017-02-07  7:52 ` Ulrich Mueller
2017-02-07  8:20   ` Kent Fredric
2017-02-07  9:28     ` Michał Górny
2017-02-07 13:27   ` Michael Orlitzky
2017-02-07 15:14     ` Ian Stakenvicius
2017-02-07 15:47       ` Ulrich Mueller
2017-02-07 17:00       ` Rich Freeman
2017-02-07 21:07         ` Ian Stakenvicius
2017-02-08  1:24         ` Sam Jorna
2017-02-08  2:11           ` Rich Freeman
2017-02-08  2:46             ` Sam Jorna

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=68433328-e9a2-03ec-bad7-c81a0d8f442c@gentoo.org \
    --to=mjo@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