Jump to content

Photo

Use or not of Make.conf file


Best Answer Oleg Vinichenko , 25 August 2017 - 04:59 PM

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.

Go to the full post »


2 replies to this topic

#1
valerievonck

valerievonck

    Newbie

  • Members
  • Pip
  • 4 posts

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...



#2
Oleg Vinichenko

Oleg Vinichenko

    Staff

  • Moderators
  • 410 posts
✓  Best Answer

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 likes this
www.funtoo.org

#3
valerievonck

valerievonck

    Newbie

  • Members
  • Pip
  • 4 posts

Ok :)

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

My mistake,

Thank you for the swift reply!





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users