public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] USE flags information resource
Date: Wed, 27 Dec 2006 11:38:36 +1000	[thread overview]
Message-ID: <7bef1f890612261738l51b533f5j7365c5a2b116307f@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]

After about a year of using Gentoo, I am very pleased.  Not being a
programmer, I do tend to spend alot of time on that learning curve.  It has
become more and more apparent in the past couple of months that USE flags
really *are* as fantastic as they are cracked up to be, in at least one
way---they enable the tuning of each package within whatever parameters are
available for that package.  Nothing even close to that is available on
other distros I have used (well, slackware had at least emacs-nox, I
guess).

Like my 4 year old son, I learn about the system by pounding on keys.  I
have always tended to tank up on caffeine before an install session, and
install everything I can get my hands on.   Some of them wouldn't work, but
that was just, as I understood, the law of probability in action.  I have
been getting wiser and wiser at fixing broken merges, and often it has
required to take some time, read the output, and reinstall some dependency
with a USE flag enabled or disabled.  I have been learning to take it slow
in installing packages, check out the situation before doing the actual
merge itself.  This is just as important as the docs said, despite my hurly
burly approach.

I have had it in mind to post about this, but now I think I have a
suggestion that may be useful:

I wiki about USE flags would be extremely useful.  Am I the only one, or are
newbies the only ones who encounter USE flags with cryptic significance?
The descriptions from euse, profuse, etc., are a bit of a help alot of the
time; however, some use flags would bear some serious explanation!   Is
something now available that would provide this functionality?  I am not
wise to the world of wikis (my sole attempt to edit wikipedia was a dismal
failture, even though I am pretty literate in LaTeX); however I would be
willing to put something simple together with some help.

Alan

-- 
Alan Davis, Kagman High School, Saipan  lngndvs@gmail.com     1-670-256-2043

I consider that the golden rule requires that if I like a program I must
share it with other people who like it.
                                          --------Richard Stallman

[-- Attachment #2: Type: text/html, Size: 2580 bytes --]

             reply	other threads:[~2006-12-27  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-27  1:38 Alan E. Davis [this message]
2006-12-27  2:00 ` [gentoo-user] USE flags information resource Thomas Tuttle
     [not found] ` <4597A9E7.10505@planet.nl>
2007-01-01  3:52   ` Alan E. Davis
2007-01-01 11:25     ` Strong Cypher
2007-01-02  7:37     ` Alan McKinnon
2007-01-02 13:35       ` Alan E. Davis
2007-01-02 14:59         ` 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=7bef1f890612261738l51b533f5j7365c5a2b116307f@mail.gmail.com \
    --to=lngndvs@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