| View previous topic :: View next topic |
| Author |
Message |
FizzyWidget
Veteran
Joined: 21 Nov 2008
Posts: 1133
Location: 127.0.0.1
|
 Posted: Tue Nov 11, 2014 12:53 pm Post subject: package.use or make.conf for use flags? |
 |
|
Which do people prefer? I know in package.use you can have a more singular usage of useflags which would be specific to the program, where as make.conf will pull in and allow any program to use the useflag in question, I am just wondering which people use, I mean if I add samba to make.conf then everything will have access to the local network, does every program that has the samba useflag actually require local net access?
_________________
I know 43 ways to kill with a SKITTLE, so taste my rainbow bitch. |
|
| Back to top |
|
 |
sera
Retired Dev
Joined: 29 Feb 2008
Posts: 1017
Location: CET
|
| Posted: Tue Nov 11, 2014 1:15 pm Post subject: |
|
|
| Since a few years Portage supports wildcards in package.use, so no need to set useflags in make.conf anymore. In fact I consider setting useflags in make.conf bad practise. |
|
| Back to top |
|
|
FizzyWidget
Veteran
Joined: 21 Nov 2008
Posts: 1133
Location: 127.0.0.1
|
| Posted: Tue Nov 11, 2014 1:17 pm Post subject: |
|
|
| sera wrote: | | Since a few years Portage supports wildcards in package.use, so no need to set useflags in make.conf anymore. In fact I consider setting useflags in make.conf bad practise. |
I have always used package.use myself, just setting up a system for a friend who is interested, and he asked, guess I will stick with package.use then 
_________________
I know 43 ways to kill with a SKITTLE, so taste my rainbow bitch. |
|
| Back to top |
|
|
Anon-E-moose
Advocate
Joined: 23 May 2008
Posts: 4774
Location: Dallas area
|
| Posted: Tue Nov 11, 2014 1:34 pm Post subject: |
|
|
I use make.conf for global flags, and package.use for package specific flags.
_________________
PRIME x570-pro, 3700x, RX 550 & 560 - 5.8 zen kernel
Acer E5-575 (laptop), i3-7100u - i965 - 5.5 zen kernel
---both---
gcc 9.3.0, profile 17.1 (no-pie & modified) amd64-no-multilib, eudev, openrc, openbox, palemoon |
|
| Back to top |
|
|
FizzyWidget
Veteran
Joined: 21 Nov 2008
Posts: 1133
Location: 127.0.0.1
|
| Posted: Tue Nov 11, 2014 1:35 pm Post subject: |
|
|
| Anon-E-moose wrote: | | I use make.conf for global flags, and package.use for package specific flags. |
Same, for things like -qt -kde and the such I use make.conf
_________________
I know 43 ways to kill with a SKITTLE, so taste my rainbow bitch. |
|
| Back to top |
|
|
sera
Retired Dev
Joined: 29 Feb 2008
Posts: 1017
Location: CET
|
| Posted: Tue Nov 11, 2014 1:46 pm Post subject: |
|
|
Introducing a new user it's even more important to avoid make.conf as a location for useflags as otherwise you have explain the broken distinction of global vs local useflags which only makes sense due to how this historically was handled.
'*/* samba -qt -kde' in package.use is the same as 'USE="samba -qt -kde"' in make.conf but doesn't need any additional concept to explain and you have all in one place. |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6378
|
| Posted: Tue Nov 11, 2014 3:18 pm Post subject: |
|
|
| sera wrote: | | '*/* samba -qt -kde' in package.use is the same as 'USE="samba -qt -kde"' in make.conf |
Not quite: You cannot easily edit/view the former with ufed. IMHO this is an important point.
| Quote: | | but doesn't need any additional concept to explain |
Neither does make.conf. It is completely up to you whether you want to make a distinction of local and global USE flags. |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7632
Location: Goose Creek SC
|
| Posted: Tue Nov 11, 2014 3:23 pm Post subject: |
|
|
@ sera
where is this new feature, */* , documented? not found in the handbook for package.use.
with
| Code: | foo/bar kde
*/* samba -qt -kde |
in package.use is foo/bar built with kde support or not?
_________________
Defund the FCC. |
|
| Back to top |
|
|
sera
Retired Dev
Joined: 29 Feb 2008
Posts: 1017
Location: CET
|
| Posted: Tue Nov 11, 2014 4:30 pm Post subject: |
|
|
| mv wrote: | | sera wrote: | | '*/* samba -qt -kde' in package.use is the same as 'USE="samba -qt -kde"' in make.conf |
Not quite: You cannot easily edit/view the former with ufed. IMHO this is an important point.
|
I guess ufed can't handle package.use being a directory either then? So be it but a fair point.
| Quote: |
| Quote: | | but doesn't need any additional concept to explain |
Neither does make.conf. It is completely up to you whether you want to make a distinction of local and global USE flags. |
I take it you agree with me that global and local don't mean what one would intuitively take it for. It's a continued source of confusion. I'm afraid we won't get rid of this terminology otherwise, which I think would be desirable. |
|
| Back to top |
|
|
sera
Retired Dev
Joined: 29 Feb 2008
Posts: 1017
Location: CET
|
| Posted: Tue Nov 11, 2014 4:36 pm Post subject: |
|
|
| DONAHUE wrote: | @ sera
where is this new feature, */* , documented? not found in the handbook for package.use.
|
'man 5 portage' seems to only hint the feature. Wouldn't call the feature new though
| Quote: | | Code: | foo/bar kde
*/* samba -qt -kde |
in package.use is foo/bar built with kde support or not? |
without kde |
|
| Back to top |
|
|
dataking
Apprentice
Joined: 20 Apr 2005
Posts: 251
|
| Posted: Tue Nov 11, 2014 5:44 pm Post subject: |
|
|
| sera wrote: |
| Quote: | | Code: | foo/bar kde
*/* samba -qt -kde |
in package.use is foo/bar built with kde support or not? |
without kde |
And this is where I see better separation between "global" and "local' USE scenarios, where "global" use flags are in make.conf and "local" use flags are in package.use.
Example: wireshark expects gtk2 OR gtk3 OR qt4, and won't accept any combination thereof. So with "-gtk -gnome qt4" in make.conf, the wireshark ebuild still complains. Putting "wireshark -gtk2 -gtk3 qt4" in package.use allows wireshark to build. In other words, it seems that specific USE flags in package.use override generic use flags in make.conf.
_________________
-= the D@7@k|n& =- |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 46069
Location: 56N 3W
|
| Posted: Tue Nov 11, 2014 7:01 pm Post subject: |
|
|
sera,
Isn't package.use ignored by emerge --info too?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
sera
Retired Dev
Joined: 29 Feb 2008
Posts: 1017
Location: CET
|
| Posted: Tue Nov 11, 2014 8:06 pm Post subject: |
|
|
dataking,
just make it | Code: | */* samba -qt -kde
foo/bar kde |
and bar will be built with use kde.
Later entries override earlier ones which has always been the case for package.use. So it's at the top of the file instead of in a different one. Not a leap step me thinks. |
|
| Back to top |
|
|
sera
Retired Dev
Joined: 29 Feb 2008
Posts: 1017
Location: CET
|
| Posted: Tue Nov 11, 2014 8:11 pm Post subject: |
|
|
NeddySeagoon,
emerge --info ignores anything in package.use. That's why it's important to ask for 'emerge --info =${P}' instead. |
|
| Back to top |
|
|
|
Installing Gentoo
