From: Jeremi Piotrowski <jeremi.piotrowski@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: a few blockers I can't figure out
Date: Wed, 2 Sep 2015 15:06:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.20.1509021442570.31496@gentoo-tp.localdomain> (raw)
In-Reply-To: <20150902045732.1def775f@a6>
On Wed, 2 Sep 2015, walt wrote:
> Thank you. I've been running systemd for months and this is the first
> time I've heard about systemd profiles. I'm not using either gnome or
> kde, so should I use default/linux/amd64/13.0/systemd, which doesn't
> seem to care if I'm running a desktop machine or a headless server?
>
I just had a closer look of the profile and it's definitely more suitable
for servers. However do remember that this is gentoo so we can work around
that.
Easy way: stay on the desktop profile and copy all of the systemd profile
files into /etc/portage:
mkdir -p /etc/portage/profile
cp /usr/portage/profiles/targets/systemd/* /etc/portage/profile
A bit harder (but way more interesting!): roll your own profile. Never
done this before and the documentation is a bit scarce, but this seems to
do the right thing:
# mkdir -p /etc/portage/repos.conf
# cat >/etc/portage/repos.conf/local.conf <<EOF
[local]
location = /usr/local/portage
auto-sync = no
EOF
# mkdir -p /usr/local/portage
# cd /usr/local/portage
# mkdir metadata profiles
# echo -e "masters = gentoo\nprofile-formats = portage-2" >metadata/layout.conf
# cd profiles
# echo "local" >repo_name
# echo -e "amd64\tdefault/linux/amd64/13.0/desktop/systemd\texp" >profiles.desc
# mkdir -p default/linux/amd64/13.0/desktop/systemd
# cd default/linux/amd64/13.0/desktop/systemd
# echo "gentoo:default/linux/amd64/13.0/desktop" >parent
# echo "gentoo:default/linux/amd64/13.0/systemd" >>parent
Then eselect your new profile and emerge -uDNva @world.
prev parent reply other threads:[~2015-09-02 13:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 4:19 [gentoo-user] a few blockers I can't figure out covici
2015-08-31 8:50 ` Neil Bothwick
2015-08-31 9:04 ` covici
2015-08-31 9:36 ` Alan McKinnon
2015-08-31 11:03 ` covici
2015-08-31 11:10 ` Alan McKinnon
2015-08-31 11:49 ` covici
2015-08-31 12:40 ` Alan McKinnon
2015-08-31 13:37 ` Alec Ten Harmsel
2015-08-31 14:03 ` covici
2015-08-31 14:53 ` Alan McKinnon
2015-08-31 16:54 ` covici
2015-08-31 17:02 ` Neil Bothwick
2015-08-31 18:12 ` covici
2015-08-31 22:18 ` Alan McKinnon
2015-09-01 0:12 ` covici
2015-09-01 9:55 ` Alan McKinnon
2015-09-01 10:15 ` Rich Freeman
2015-09-01 11:13 ` covici
2015-09-01 11:45 ` Rich Freeman
2015-09-01 11:54 ` covici
2015-09-01 10:18 ` Marc Joliet_1
2015-09-01 10:46 ` Alan McKinnon
2015-09-01 11:03 ` covici
2015-09-01 11:15 ` Alan McKinnon
2015-08-31 23:51 ` Jeremi Piotrowski
2015-09-01 0:22 ` covici
2015-09-02 11:57 ` [gentoo-user] " walt
2015-09-02 12:45 ` Rich Freeman
2015-09-02 13:06 ` Jeremi Piotrowski [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=alpine.LNX.2.20.1509021442570.31496@gentoo-tp.localdomain \
--to=jeremi.piotrowski@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