From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] necessary use flgas
Date: Thu, 25 Jun 2015 10:38:06 +0200 [thread overview]
Message-ID: <558BBDEE.5010301@gmail.com> (raw)
In-Reply-To: <CAGQH77fvH_cjKVWKorDYAcETQYA5DPL+TpyHaRHcv+KqgAhJMA@mail.gmail.com>
On 25/06/2015 06:25, Jc García wrote:
> 2015-06-24 6:23 GMT-06:00 behrouz khosravi <bz.khosravi@gmail.com>:
>>
>>> Here's some good advice:
>>>
>>> Don't do that. See below.
>>
>>
>> Oops! I have done it and I am happy so far !
>>
>>> That's a bit of a nonsensical line of thought, as what you think you
>>> want doesn't really exist.
>>
>>
>> I think you misunderstood me! for example adding CPU specific flags is a
>> good idea right?
>> I meant something like that. For example is it wise to enable opengl flag
>> globally ? is it helpful to do so?
>>
>>>
>>>> What do you recommend ?
>>>
>>> DO NOT SET "USE=-*"
>>
>>
>> As I said before I have done it and I totally recommend it to anyone
>> interested to get a better understanding of user land.
>>
> I don't see the point of using USE="-*" for learning, if you want to
> really learn, create and overlay and make your own profile, read the
> developer documentation about it, and do a proper thing, not some
> clunky mess in /etc/portage.
> You could very well evaluate the basic profile, and part from there or
> modify it as you see fit, but making a mess that you wont be able to
> port easily in case you actually make something you might want to keep
> and reproduce somewhere else, is not getting a better understanding.
>
Best way I ever found to learn how things really work under the hood is
to build a Linux From Scratch and pay close attention to every single step.
Not that you'd ever actually *use* that system - there's no sane package
management for a start - but after building an LFS, the content of
ebuilds in @system starts to make a lot more sense; you can see why some
of the decisions in the profiles were made; and make.conf now appears in
a whole new light.
Then take the valuable lessons from LFS and apply them appropriately to
using Gentoo. These things are tools and the best workmen are always
very familiar with their tools as a co-ordinated whole (as opposed to a
bunch of mish-mash stuff cluttering up a toolbox)
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2015-06-25 8:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 13:05 [gentoo-user] necessary use flgas behrouz khosravi
2015-06-23 13:38 ` Neil Bothwick
2015-06-23 14:45 ` David Haller
2015-06-23 15:31 ` Neil Bothwick
2015-06-23 16:35 ` David Haller
2015-06-23 17:08 ` Neil Bothwick
2015-06-23 18:06 ` David Haller
2015-06-23 17:22 ` [gentoo-user] " James
2015-06-23 19:09 ` David Haller
2015-06-24 10:57 ` [gentoo-user] " Franz Fellner
2015-06-24 11:59 ` behrouz khosravi
2015-06-25 8:25 ` Neil Bothwick
2015-06-24 11:13 ` Alan McKinnon
2015-06-24 11:50 ` Alec Ten Harmsel
2015-06-24 12:09 ` Alec Ten Harmsel
2015-06-24 12:29 ` Alec Ten Harmsel
2015-06-25 4:10 ` [gentoo-user] " »Q«
2015-06-25 8:09 ` [gentoo-user] " Alan McKinnon
2015-06-25 8:27 ` Dale
2015-06-25 8:32 ` Alan McKinnon
2015-06-28 2:16 ` Dale
2015-06-24 12:23 ` behrouz khosravi
2015-06-25 4:25 ` Jc García
2015-06-25 8:38 ` Alan McKinnon [this message]
2015-06-25 12:01 ` behrouz khosravi
2015-06-25 12:56 ` Rich Freeman
2015-06-25 15:33 ` Emanuele Rusconi
2015-06-26 5:44 ` [gentoo-user] necessary use flags Thomas Mueller
2015-06-25 5:43 ` [gentoo-user] necessary use flgas Walter Dnes
2015-06-25 8:29 ` Alan McKinnon
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=558BBDEE.5010301@gmail.com \
--to=alan.mckinnon@gmail.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