public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Vaeth <martin@mvath.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Profile listings
Date: Mon, 22 Jun 2015 14:47:05 +0000 (UTC)	[thread overview]
Message-ID: <mm9759$4q8$1@ger.gmane.org> (raw)
In-Reply-To: loom.20150622T151848-436@post.gmane.org

James <wireless@tampabay.rr.com> wrote:
> There is no dir '/var/portage' on my system. Yet this command works fine:
>
> "PORTAGE_PROFILE=/var/portage/profiles/default/linux/arm/13.0/armv7a eix -c
> --system "
>
> Strange, to say the least.

Not at all strange: Again, PORTAGE_PROFILE points to a non-directory,
so it is ignored, and the default is chosen.

>> > But it's a stupid place for it to go on Linux and most of the sane
>> > technical Gentoo world agrees it really is a better fit in /var/portage.
>
> "pig-mess" like I said earlier.

A default is a default. It is you - the sytem adminstrator - who is
responsible to determine the setting most appropriate for his system.
For instance, when exporting, a sane place might be
/srv/gentoo-repo

>> Or, as I do, put it in its own partition and you can mount it wherever 
>> you like. Just point make.conf and repos.conf/gentoo.conf at it.
>
> Yea, yea, I can make a custom mess too: aka brilliantly (in my own mind)
> organize it, I mean.

That's what you are supposed to do with a meta-distribution,
especially if you do not like the default choice.

> The bottom line for me is:
>
> 1) folks should be able to migrated up and down the profile tree. It's give
> us some neat abilities. If I have a workstation that becomes old, I could
> change the profile and move it'down' to default or embedded and turn it
> into a decicated, minimized router, firewall, bridge, sniffer etc etc. I
> think the offcial word is changing profiles is not recommended.

If you don't know what you are doing, you keep the pieces:
Some conversion (e.g. non-multilib->multilib or 32bit->64bit)
are really hard. It won't help you just to change the profile:
You would need cross-compilation etc.

OTOH, if you just want to transform a desktop into a server (e.g.)
it is very simple: Mainly this has nothing to do with the profile
but with the USE-flags and packages which you select manually.

> 2) Some thing of a profile needs to exist between an embedded system
> (busybox only) and the default.

No. If you are running an embedded system, you are supposed to be
expert enough to make your own profile. If you lack the experience
to do it, don't do it, since otherwise you will just end up with a
mess anyway. Use instead one of the save profiles and do not try to
shrink it beyond sanity, so that things work and do not break
unexpectedly.

> Cleaning up the profiles just seems logical to me, after noodling
> around with in the profiles......

Fine. If you are an expert enough do it. You will have then the
experience that nobody else will have exactly your need and thus
understand that having a profile only for your need in the main
gentoo repository would be pointless. And of course, you are then
expert enough to create a custom profile (or build one modifying
an exising one) without asking here.
If you are not such an expert: See above: Use one of the save profiles
and do not try to shrink it beyond sanity, so that things work and do
not break unexpectedly.


> 5) Also, security in the cluster/cloud world is almost impossible building
> clusters on top of 'bloated OSes and bloated system packages'. YMMV.

None of the gentoo profiles is bloated (systemd excluded, of course).
And even if a package is installed which you do not need, it will not
make your system insecure if it is not used. Your configuration and
USE-flags are much more important than the tiny list of @system packeges:
Shrinking these even more is really only a task for the experienced expert.



      reply	other threads:[~2015-06-22 14:47 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
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 [this message]

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='mm9759$4q8$1@ger.gmane.org' \
    --to=martin@mvath.de \
    --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