public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] flag icu
Date: Mon, 13 Aug 2018 10:31:38 -0400	[thread overview]
Message-ID: <a0fd22c2-d850-6a89-7731-20d4a7afa9ae@verizon.net> (raw)

Hello,

Q1} In my attempts to minimize flag settings, why do I need the flag "icu" ?

+ - icu   Enable ICU (Internationalization Components for Unicode)
		support, using dev-libs/icu




Q2} Ultimately, I'm trying to discover that minimum of flags for amd64
servers and workstations, that allow them to function nominally
normal, with most flags set per package.use. The bare_bones flags really
work great for gentoo clusters. I'm specifically trying to avoid the
advanced profiles, as I intend to manage flags dynamically as frameworks
(collections of codes) are added or removed from the cluster.


Any hints on a systematic by system parsing this sort of minimized-flag
data :

 [12]  default/linux/amd64/17.0 (stable) *


would be keenly appreciated. "eselect profile list" is great. but
I need it per many different architectures and do not have one
of each of the systems I need to experiment on. How are those flag_sets
discovered in some sort of systematic approach?



James


             reply	other threads:[~2018-08-13 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 14:31 james [this message]
2018-08-13 15:36 ` [gentoo-user] flag icu Corentin “Nado” Pazdera
2018-08-13 15:47   ` james
2018-08-13 16:58     ` james
2018-08-13 17:14     ` Corentin “Nado” Pazdera
2018-08-13 18:34       ` james
2018-08-15 18:29       ` james
2018-08-13 17:17 ` [gentoo-user] " Nikos Chantziaras
2018-08-13 19:10   ` 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=a0fd22c2-d850-6a89-7731-20d4a7afa9ae@verizon.net \
    --to=garftd@verizon.net \
    --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