From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Giving Gentoo Another Go
Date: Fri, 18 Mar 2016 09:08:53 +0000 [thread overview]
Message-ID: <20160318090853.3ce763a8@digimed.co.uk> (raw)
In-Reply-To: <007601d180c2$cb440b60$61cc2220$@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
On Thu, 17 Mar 2016 23:03:47 -0400, Hunter Jozwiak wrote:
> After talking to a few diehard Gentoo fans at my local LUG, I decided I
> would like to give Gentoo another shot. Are there any good books that
> can supplement the Gentoo handbook
The Gentoo handbook really is the book. It's written by Gentoo devs so it
is always up to date, something that cannot always be said of print books
(a friend of mine wrote the Haynes Manual on Ubuntu some years ago,
few months later they released Unity!).
> as well as books that go more in
> depth than the Gentoo chapter on Portage?
The main mistake that people make with the Gentoo Handbook is that they
follow it carefully through installation, then stop. They have only read
chapter 1. The rest of the handbook, along with the Gentoo Wiki provide a
lot more information.
> One of the main issues I
> faced with Gentoo when I first tried it is that I did not understand
> the power of package.use, and I put everything in to make.conf.
No one gets it right first time, there are many choices and many ways of
doing things. No book can tell you which way is right for you, only
experience can do that. Getting things like this wrong is a natural part
of the Gentoo learning experience.
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. There's
also the choice of whether you make package.use (and its friends) and
make.conf a single file or a directory of files. Ask in here and you will
find proponents of both approaches, but it's an organisational choice,
whichever works for you is best.
--
Neil Bothwick
"Mmmm, trouble with grammer have I, yes?" - Yoda
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-03-18 9:09 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 [this message]
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 ` [gentoo-user] " James
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=20160318090853.3ce763a8@digimed.co.uk \
--to=neil@digimed.co.uk \
--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