From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Profile listings
Date: Fri, 19 Jun 2015 19:56:53 +0000 (UTC) [thread overview]
Message-ID: <loom.20150619T214734-686@post.gmane.org> (raw)
In-Reply-To: CA+wBphLDeSaw5MxMJL-J7w3fRncjJ5NuNNRLF5nSoMwckvHpsg@mail.gmail.com
Bruce Schultz <brulzki <at> gmail.com> writes:
> Note that default/linux/arm/13.0/armv7a profile is building on the
> arch/arm/armv7a (what you searched against).
I think all possible profiles for each and every type of gentoo install
should either be readily available on any installed gentoo system, or
on the net or otherwise easy to parse.
> As I understand it, the profiles in arch/arm don't contain any packages
files, so there's no <at> system packages to list (as you found). I presume
that the arch/arm/... profiles are intended to define compiler flags etc for
cpu variants, and are used as a basis of a more complete profile (such as
default/linux/arm/13.0/armv7a). If you look through
/usr/portage/profiles/profiles.desc, you see the list of all profiles which
would be selectable through 'eselect profile', and I don't find and arch/...
profiles listed in there.
Correct. It's an inconsistent mess, imho. Being able to readily parse
the packages on a given (arch/processor/profile) install would be a keen
tool before making hardware purchases. Embedded to full distro are blurring
the landscape, particularly as arm64 emerges. Also, my cluster build work is
surprisingly revealing that HPC and general prupose clusters are best build
on bare metal or embedded linux systems, particularly but not limited to
performance gains. Gentoo use to "king" in the embedded linux space
and it's an odd (for sure) reality that building clusters, clouds or data
centers on embedded linux is moving forward at a very rapid pace.
I certainly do not wish to alienate or detract from the excellent work our
dev community has achieved. But, embedded (gentoo) linux and cluster/cloud
computing could easily put gentoo on top of the heap again. Surely gentoo is
uniquely positioned to build clusters that are not on top of 'bloatware'!
> Hope that helps...
> Bruce
YES, and I appreciated every comment!
later,
James
next prev parent reply other threads:[~2015-06-19 19:57 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 ` [gentoo-user] " James
2015-06-15 12:15 ` 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 [this message]
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.20150619T214734-686@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