public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Machine completely broken; Ncursed!
Date: Mon, 13 Apr 2015 22:38:10 -0500	[thread overview]
Message-ID: <20150413223810.4bac3e1c@sepulchrave.remarqs> (raw)
In-Reply-To: 552B59B6.9040206@gmail.com

On Mon, 13 Apr 2015 07:52:54 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> On 13/04/2015 03:38, »Q« wrote:
> > On Sun, 12 Apr 2015 21:24:48 -0400
> > Alec Ten Harmsel <alec@alectenharmsel.com> wrote:

> >> Also, using the KDE profile and having USE="-*" seem contrary. One
> >> of the main reasons to use a profile is to get a relevant set of
> >> USE flags.
> > 
> > I don't want the profile's USE flags, but I still thought it best to
> > select the profile that matches what I use the machine for.
>  
> A profile is indeed intended to match the intended use of the machine,
> and to do that it does two things:
> 
> - enables or disables some software (the minor feature)
> - sets some sane default USE (the major feature)
> 
> USE="-*" essentially undoes the profile entirely rendering it useless.
> You'd be better off just setting your profile to default and doing all
> the heavy lifting yourself instead of going with the maintainers
> suggestions implemented in the profile.

I rarely have to mess with changing USE flags as it is now, but setting
them up from scratch (something I haven't done in many years) after
clobbering the profile's defaults was heavy lifting, for me at least.
If I ever have to do it again, I'll check out using a simpler profile
without clobbering its USE.



  reply	other threads:[~2015-04-14  3:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 14:22 [gentoo-user] Machine completely broken; Ncursed! Alan Grimes
2015-04-11 14:34 ` Neil Bothwick
2015-04-11 17:22   ` Mick
2015-04-11 19:41   ` Alan Grimes
2015-04-11 21:27     ` Neil Bothwick
2015-04-11 20:04 ` Andreas K. Huettel
2015-04-12  0:42   ` Alan Grimes
2015-04-12  0:58     ` [gentoo-user] " walt
2015-04-12  1:02     ` [gentoo-user] " Peter Humphrey
2015-04-12  1:58     ` Dale
2015-04-12  9:12     ` J. Roeleveld
2015-04-12 17:23       ` [gentoo-user] " »Q«
2015-04-12 18:35         ` Matti Nykyri
2015-04-13  1:07           ` »Q«
2015-04-13  5:48             ` Alan McKinnon
2015-04-14  2:08               ` »Q«
2015-04-12 20:07         ` J. Roeleveld
2015-04-13  1:15           ` »Q«
2015-04-13  1:24             ` Alec Ten Harmsel
2015-04-13  1:38               ` »Q«
2015-04-13  1:52                 ` Alec Ten Harmsel
2015-04-14  1:55                   ` »Q«
2015-04-13  5:52                 ` Alan McKinnon
2015-04-14  3:38                   ` »Q« [this message]
2015-04-13  7:51                 ` Neil Bothwick
2015-04-14  3:51                   ` »Q«
2015-04-14  7:47                     ` Neil Bothwick
2015-04-15  3:09                       ` »Q«
2015-04-15  8:24                         ` Neil Bothwick
2015-04-12  9:31     ` [gentoo-user] " Neil Bothwick
2015-04-12 14:13     ` Andreas K. Huettel
2015-04-11 23:23 ` Fernando Rodriguez
2015-04-12  1:25   ` Alan Grimes
2015-04-12  0:06 ` Peter Humphrey
2015-04-12  1:27   ` Alan Grimes
2015-04-12 14:52     ` Peter Humphrey
2015-04-16  2:40 ` Fernando Rodriguez

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=20150413223810.4bac3e1c@sepulchrave.remarqs \
    --to=boxcars@gmx.net \
    --cc=gentoo-user@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