Harry Putnam <rea...@newsguy.com> wrote:

> Harry Putnam <rea...@newsguy.com> writes:
> 
> [...]
> 
> > If this is to be a `personal use' HOST and I eventually want an  LXDE
> > desktop, , which is the smart profile to chose? 2?
> 
> Thanks for the input posters.
> 
> NOTE: I am installing from SystemRescueCD-5-BETA
> 
> Following along with the `quick install' document:
> When I got chrooted in I see the profile list is actually much longer:
> 
> Available profile symlink targets:
>   [1]   default/linux/x86/13.0
>   [2]   default/linux/x86/13.0/selinux
>   [3]   default/linux/x86/13.0/desktop
>   [4]   default/linux/x86/13.0/desktop/gnome
>   [5]   default/linux/x86/13.0/desktop/gnome/systemd
>   [6]   default/linux/x86/13.0/desktop/kde
>   [7]   default/linux/x86/13.0/desktop/kde/systemd
>   [8]   default/linux/x86/13.0/developer *
>   [9]   hardened/linux/x86
>   [10]  hardened/linux/x86/selinux
>   [11]  hardened/linux/musl/x86
>   [12]  default/linux/uclibc/x86
>   [13]  hardened/linux/uclibc/x86
> 
> It appears what several people suggested (2) is no longer what 2 used
> to be.  Or at least it is on SystemRescueCD.
> 
> I chose 8 since I want developement tools onboard and since it does
> not specify a desktop I'm guessing it would work like 1 or 3 in that
> regard.
> 
> Anyone know if that is true?
> 
> Does this have some impact on what gets installed?
> 
> Also what actually happens when a profile is selected?
> 
> Should I see a set of USE flags appear in /etc/portage/make.conf or
> something like that?
> 
> As it is I didn't notice any change in /etc/portage/make.conf.
> 
> All I see there for USE is:
> 
> ,----
> | # These are the USE flags that were used in addition to what is provided by 
> the
> | # profile used for building.
> | USE="bindist
> `----
> 

I would not use that profile -- its gentoo development they are talking
about if memory serves, so I would pick 13.0/default/linux/desktop (3).


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         cov...@ccs.covici.com

Reply via email to