Use or not of Make.conf file

[valerievonck]

Just a question, not wanting to start a discussion nor a flamewar.

I have been a long time Gentoo user, and I am used to do everything to do with : /etc/portage/make.conf,

I know that people are going to say, Funtoo != Gentoo, I could not agree more, it is fast & lean, just how an OS must be.

A staff member said: 

 

 you shouldn't put anything into make.conf. you need to sync again and there should be ego update to 1.1.3-r5

 

I respect his opinion,  but why is Funtoo taken this approach (to move away from make.conf) or why I am not getting it, 

I am trying to understand and learn...

If I do not set my makeopts, will Funtoo be able to determine my (virtual) cpu's?

 

Just wondering...

[Oleg Vinichenko]

that quote was for not putting python targets entries into make.conf (by anything python related meant). Of course, you can put them, it's allowed, as well as adding any other system-wide settings. by default the make.conf is empty.

[valerievonck]

Ok :)

My misunderstanding, I thought you meant, leave the make.conf empty...  :huh:

My mistake,

Thank you for the swift reply!

[palica]

On 25.8.2017 at 6:28 PM, valerievonck said:

If I do not set my makeopts, will Funtoo be able to determine my (virtual) cpu's?

yes, should be set automatically.

[Sandro]

I use make.conf; I started to write it in 2010 using Gentoo; then I use it also if  may be "redundant" about some use flags; and i've a lot of USE and ~ 2000 ebuilds installed. Cause i like to have as more as possible the status and configuration of my system under my eyes :)