public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Machine completely broken; Ncursed!
Date: Sun, 12 Apr 2015 21:24:48 -0400	[thread overview]
Message-ID: <552B1AE0.5030507@alectenharmsel.com> (raw)
In-Reply-To: <20150412201552.3e0aca16@sepulchrave.remarqs>



On 04/12/2015 09:15 PM, »Q« wrote:
>
> Before you pore through it, I guess I should point out that it's not
> causing me any problems -- I was just curious about why it would be a
> bad idea for me to manage those PYTHON_* variables myself.  I guess the
> most notable thing about my make.conf is that I'm one of those crazy
> USE="-*" people.
>


It's not a bad idea to manage the PYTHON_TARGETS, PYTHON_SINGLE_TARGET,
and RUBY_TARGET variables if you *need* a specific version of python or
ruby. If you do not, I would say it is bad. These are set in the profile
so that the maintainers can decide when to update to a new stable
version. Since all of the various python and ruby libraries are
installed from source, it's generally a good idea to wait for the
maintainers to stabilize a certain version since that means the library
support is also good.

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.

Alec


  reply	other threads:[~2015-04-13  1:24 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 [this message]
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«
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=552B1AE0.5030507@alectenharmsel.com \
    --to=alec@alectenharmsel.com \
    --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