From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Profile listings
Date: Mon, 15 Jun 2015 04:37:50 +0000 (UTC) [thread overview]
Message-ID: <loom.20150615T062801-269@post.gmane.org> (raw)
In-Reply-To: 20150615021218.442abc3967649188f0233b94@gentoo.org
Andrew Savchenko <bircoph <at> gentoo.org> writes:
> Profile do all the stuff that can be done or overridden
> in /etc/portage, but they define some sane "default" sets of
> settings for common profiles.
> USE="-*" will override all USE settings in your profile. As you were
> already warned, this may break stuff: e.g. expected
> functionality will not be available or package will refuse to build
> if it needs at least one of USE flags set (e.g. alternative foo
> providers). So you must test things very carefully with USE="-*".
yes,
of coarse.
> A set of default packages is defined in the "packages" file of each
> profile. Profiles usually have "parent" file which lists parent
> profiles: they are inherited, but may be overridden here and there
> in a child profile.
Yes.
This is why I was looking for a 'tool' or script that would allow me
to easily browse the default package listings for the different
arch types with a default profile. In fact, I bet I can trim out
even more packages, or figure what what I need to add back in after
"-*" on a given chipset/arch_family.
> If you want an absolutely minimal system, after you have set it up
> you may remove some packages even from the <at> system set. E.g. if
> you're sure you don't need man or ssh, remove corresponding
> packages. Just be careful here since it is easy to brick your
> system here.
Yes, I keep old boxes around just to burn a bit and re_install (x86 first).
I bet you have done this before. recently on amd64 or arm64?
> Best regards,
> Andrew Savchenko
TIA,
James
next prev parent reply other threads:[~2015-06-15 4:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 19:22 [gentoo-user] Profile listings James
2015-06-14 20:40 ` Andreas K. Huettel
2015-06-14 22:21 ` [gentoo-user] " James
2015-06-14 23:38 ` Andreas K. Huettel
2015-06-15 4:27 ` James
2015-06-14 23:12 ` [gentoo-user] " Andrew Savchenko
2015-06-15 4:37 ` James [this message]
2015-06-15 12:15 ` [gentoo-user] " Martin Vaeth
2015-06-15 15:25 ` James
2015-06-16 17:42 ` James
2015-06-16 20:26 ` Neil Bothwick
2015-06-17 8:18 ` Martin Vaeth
2015-06-17 16:11 ` James
2015-06-18 7:05 ` Martin Vaeth
2015-06-18 15:21 ` James
2015-06-18 17:33 ` Martin Vaeth
2015-06-18 18:44 ` James
2015-06-18 19:59 ` Martin Vaeth
2015-06-19 19:46 ` James
2015-06-21 3:29 ` Jonathan Callen
2015-06-21 16:17 ` James
2015-06-19 2:27 ` Bruce Schultz
2015-06-19 19:56 ` James
2015-06-19 20:38 ` Neil Bothwick
2015-06-20 2:51 ` James
2015-06-21 16:09 ` James
2015-06-21 17:49 ` Neil Bothwick
2015-06-21 20:02 ` Alan McKinnon
2015-06-21 23:53 ` Peter Humphrey
2015-06-22 13:38 ` James
2015-06-22 14:47 ` Martin Vaeth
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.20150615T062801-269@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