From: Willie Wong <wwong@Princeton.EDU>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Changing profiles
Date: Tue, 23 Dec 2008 12:51:37 -0500 [thread overview]
Message-ID: <20081223175137.GA11074@princeton.edu> (raw)
In-Reply-To: <49bf44f10812230755y1f809a30j1cf83e0d40a7ca04@mail.gmail.com>
On Tue, Dec 23, 2008 at 07:55:20AM -0800, Penguin Lover Grant squawked:
> I'm really surprised to hear that. Can I switch my laptop from a
> hardened profile to a non-hardened one? I know I've been told I can't
> do that.
I don't know much about amd64, so I don't know how the 'multilib'
thing would work. But in so far as switching from a hardened profile
to a non-hardened one and vice versa: the answer is yes and no.
Going from hardened to non-hardened is generally easier, I think.
The available packages from hardened is generally a subset of the ones
from non-hardened. So once you switch profiles you'd be prompted to
upgraded GCC and many other packages, and you'll find a few more (and
possibly a few fewer) USE to work with. Most of these will fix itself
over time.
Going from non-hardened to hardened may run into some downgrading
problems, however, in view of the above. For example, hardened devs
still have not put gcc4 in stable (at least on x86, I don't know about
amd64), so if you have gcc4 installed, you'll need to downgrade. Along
the same lines some packages that will not compile unless you use gcc4
cannot be installed (lilypond for example).
I suggest that you compare and contrast the package.mask and
package.use.mask (and possibly make.defaults) files in the
/usr/portage/profiles/{hardened,default/linux} directories to see what
differences there are.
> You think an 'eselect profile set 2 && emerge -e world' will
> accomplish the entire thing?
Is emerge -e world even necessary? (Someone correct me if I am wrong.)
My understanding is that switching profiles between hardened and
non-hardened does not cause such drastic change to the toolchain that
you must rebuild everything now. I am pretty sure when I switched my
desktop to hardened I just let it gradually phase in.
HTH,
W
--
"What are you talking about? "
"Never mind, eat the fruit. "
"You know, this place almost looks like the Garden of Eden.
"
"Eat the fruit. "
"Sounds quite like it too. "
Sortir en Pantoufles: up 746 days, 16:20
next prev parent reply other threads:[~2008-12-23 17:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 15:12 [gentoo-user] Changing profiles Grant
2008-12-23 15:22 ` Albert Hopkins
2008-12-23 15:28 ` Grant
2008-12-23 15:45 ` Albert Hopkins
2008-12-23 15:55 ` Grant
2008-12-23 16:49 ` Albert Hopkins
2008-12-23 17:03 ` Grant
2008-12-23 17:38 ` Grant
2008-12-23 21:38 ` Neil Bothwick
2008-12-23 16:57 ` James Stull
2008-12-23 17:28 ` Volker Armin Hemmann
2008-12-23 17:40 ` Grant
2008-12-23 18:16 ` Volker Armin Hemmann
2008-12-23 21:39 ` Neil Bothwick
2008-12-24 1:54 ` Dale
2008-12-24 17:01 ` Grant
2008-12-24 17:16 ` Dale
2008-12-26 20:05 ` Neil Bothwick
2008-12-26 20:32 ` Grant
2008-12-27 0:51 ` Neil Bothwick
2008-12-27 15:35 ` Grant
2008-12-26 20:07 ` Neil Bothwick
2008-12-23 17:51 ` Willie Wong [this message]
2008-12-23 19:53 ` Alan McKinnon
2008-12-23 20:05 ` Grant
2008-12-23 20:16 ` Alan McKinnon
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=20081223175137.GA11074@princeton.edu \
--to=wwong@princeton.edu \
--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