public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  emerge advises upgrade profile
Date: Mon, 26 Oct 2009 23:52:47 -0500	[thread overview]
Message-ID: <4AE67C9F.7060103@gmail.com> (raw)
In-Reply-To: <1256608357.10355.24.camel@bunyip.localdomain>

W.Kenworthy wrote:
> On Tue, 2009-10-27 at 01:52 +0200, Alan McKinnon wrote:
>   
>> On Tuesday 27 October 2009 01:48:22 William Kenworthy wrote:
>>     
>>> rattus ~ # eselect profile list
>>> Available profile symlink targets:
>>>   [1]   default/linux/x86/10.0 *
>>>   [2]   default/linux/x86/10.0/desktop
>>>   [3]   default/linux/x86/10.0/developer
>>>   [4]   default/linux/x86/10.0/server
>>>   [5]   hardened/linux/x86/10.0
>>>   [6]   selinux/2007.0/x86
>>>   [7]   selinux/2007.0/x86/hardened
>>>   [8]   selinux/v2refpolicy/x86
>>>   [9]   selinux/v2refpolicy/x86/desktop
>>>   [10]  selinux/v2refpolicy/x86/developer
>>>   [11]  selinux/v2refpolicy/x86/hardened
>>>   [12]  selinux/v2refpolicy/x86/server
>>> rattus ~ #
>>>       
>> In almost all cases [2] or [4] is a better choice than [1]
>>
>>
>>
>>     
>
> I wouldnt think so - I have a lot of server apps and desktop apps, even
> on my laptop and main server at home.  I dont have such a thing as a
> pure server or a pure desktop so I stuck with this.  I did change to
> desktop once on my laptop and didnt like the number of changes I would
> need to revert so didnt proceed.  I my personal opinion is that having
> developer, server and desktop profiles for gentoo is just stupid.
> redhat/Mandrake etc have had this for a long time and they just are a
> way to start customising the system - dont save much at all.  
>
> I guess the question is where do you start customising from? - a
> desktop, a server or gentoo 1.1b circa 1999 (if memory serves me
> correctly) which is where some of my systems (including the one above)
> started :)
>
>
> BillK
>
>   

Well, I read you can put something in your make.conf USE line that
disables most of the profile.  I think it is
"-*" or something like that.  It disables the USE part at least.  You
can then start with basically nothing and build your own. 

Want to hear something else funny, there is talk of having a KDE profile
and some have mentioned a Gnome profile as well. 

No matter what you chose to use, you can still override the settings if
you need to.  That's what make.conf is for. 

Dale

:-)  :-) 



  reply	other threads:[~2009-10-27  4:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 23:31 [gentoo-user] emerge advises upgrade profile Harry Putnam
2009-10-26 23:36 ` Crístian Viana
2009-10-26 23:40 ` Sebastian Beßler
2009-10-26 23:48 ` Alan McKinnon
2009-10-27  0:23   ` Dale
2009-10-26 23:48 ` William Kenworthy
2009-10-26 23:52   ` Alan McKinnon
2009-10-27  1:52     ` W.Kenworthy
2009-10-27  4:52       ` Dale [this message]
2009-10-27  3:23     ` [gentoo-user] " Harry Putnam
2009-10-27  5:33       ` Jonathan Callen
2009-10-28 16:43         ` Harry Putnam
2009-10-27  8:41       ` Alan McKinnon
2009-10-27  8:46         ` Justin
2009-10-28 16:52         ` Harry Putnam
2009-10-28 16:59           ` Alan McKinnon
2009-10-28 22:03             ` Dale
2009-10-28 23:43               ` 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=4AE67C9F.7060103@gmail.com \
    --to=rdalek1967@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