From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Giving Gentoo Another Go
Date: Fri, 18 Mar 2016 16:21:09 +0000 (UTC) [thread overview]
Message-ID: <loom.20160318T165724-113@post.gmane.org> (raw)
In-Reply-To: 20160318120346.21b9e5e6@digimed.co.uk
Neil Bothwick <neil <at> digimed.co.uk> writes:
>
> On Fri, 18 Mar 2016 10:09:14 +0000, Peter Humphrey wrote:
>
> > > You will develop your way of doing things over time, and that way
> > > could change as your needs do. Using your example of package.use,
> > > moving USE flags from package.use to make.conf is an easy enough task
> > > if you need to change. I tend to put them n package.use to start with
> > > then migrate to make.conf if I find I am using the same flag on
> > > several packages.
The entire /etc/make.conf directory is parses, so you can take package.use
and make a dir out of it and then logically organize your flags into several
directories, once a system get's large and complex.
> > A simple way to start off is to see whether the USE flag is listed in
> > /usr/portage/profiles/use.desc or use.local.desc. If the former, it's
> > likely to affect many packages in a typical system so put it in
> > make.conf; if the latter, it's likely to affect only a few of your
> > packages so put it in package.use. You can always move it later if you
> > want to, as Neil says.
> app-portage/euses is an easy way of looking up USE flags, give it the
> name of a flag and it shows you the description. If it shows one or more
> package names, the USE flag is defined in local.desc.
All good information. The exciting thing happening in Gentoo right now,
is some of the devs are promoting the concept of 'lazy flags'. This
basically means some new and additional features will be added to portage
or the Packaage Management system (portage, paludis, etc) where additional
user defined logic will 'automagically' make default and necessary
modifications to flag configurations, and the user just reviews those
'auto-enhancements' or something like that.
Gentoo never stops innovating, but the caveat is you have to be patient and
invest of yourself into learning Gentoo.
Gentoo is an addiction, which most of us are quite happy with. Gentoo also
has legendary status with many of the brightest minds in computer science,
for a myriad of valid reasons. Gentoo is something that is wonderful to be a
part of and is an 'honor_badge' of fortitude because one can deeply learn
about linux, software and a host of relevant technologies quite readily in a
Gentoo environment.
Gentoo's future is very bright, unique and most rewarding. Gentoo is my pal
and my best friend and what I use to earn money.
hth,
James
prev parent reply other threads:[~2016-03-18 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 3:03 [gentoo-user] Giving Gentoo Another Go Hunter Jozwiak
2016-03-18 6:07 ` Alan McKinnon
2016-03-18 15:29 ` Stroller
2016-03-18 22:04 ` Alan McKinnon
2016-03-18 6:17 ` Gregory Woodbury
2016-03-18 9:08 ` Neil Bothwick
2016-03-18 10:09 ` Peter Humphrey
2016-03-18 12:03 ` Neil Bothwick
2016-03-18 15:50 ` Peter Humphrey
2016-03-18 16:33 ` OT: " wabenbau
2016-03-18 16:21 ` James [this message]
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=loom.20160318T165724-113@post.gmane.org \
--to=wireless@tampabay.rr.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