On Wed, 28 Mar 2018, at 15:20, Greg Byshenk wrote:> On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote: > > On 28/03/2018 14:39, Gregory Byshenk wrote: > > > You can do this manually, or by adding a PORTS_MODULES line to > > > /etc/make.conf. This will rebuild the listed modules from ports > > > when you build a new kernel. > > > > Are you sure it's in /etc/make.conf and not /etc/src.conf? > > No. But it is in the man page for make.conf and not src.conf.yeah. That is... confusing! at least to me, because [I thought it would be] src.conf that's consulted when src is built. So I ran a couple of tests and found that it would work in either file HOWEVER if one ports module statement was in src.conf and another, different ports module statement was in make.conf, that the one in src.conf would get built but the one in make.conf would not. how confusing is that. This is on 11.1-stable. -- John tech-lists at zyxst.net
Am 28.03.18 um 17:30 schrieb John:> On Wed, 28 Mar 2018, at 15:20, Greg Byshenk wrote: >> On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote: >>> On 28/03/2018 14:39, Gregory Byshenk wrote: >>>> You can do this manually, or by adding a PORTS_MODULES line to >>>> /etc/make.conf. This will rebuild the listed modules from ports >>>> when you build a new kernel. >>> >>> Are you sure it's in /etc/make.conf and not /etc/src.conf? >> >> No. But it is in the man page for make.conf and not src.conf. > > yeah. That is... confusing! at least to me, because [I thought it would be] > src.conf that's consulted when src is built. So I ran a couple of tests and > found that it would work in either file HOWEVER if one ports module statement > was in src.conf and another, different ports module statement was in make.conf, > that the one in src.conf would get built but the one in make.conf would not. > > how confusing is that. This is on 11.1-stable.No, its not confusing at all, if you think about it ... ;-) /etc/make.conf is included in any case, but kernel and world builds will include /etc/src.conf thereafter (and overwrite earlier settings read from make.conf, unless ?= is used to preserve the earlier value, or += to append the new values). Regards, STefan
On Wed, 2018-03-28 at 16:30 +0100, John wrote:> On Wed, 28 Mar 2018, at 15:20, Greg Byshenk wrote: > > > > On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote: > > > > > > On 28/03/2018 14:39, Gregory Byshenk wrote: > > > > > > > > You can do this manually, or by adding a PORTS_MODULES line to > > > > /etc/make.conf. This will rebuild the listed modules from ports > > > > when you build a new kernel. > > > Are you sure it's in /etc/make.conf and not /etc/src.conf? > > No. But it is in the man page for make.conf and not src.conf. > yeah. That is... confusing! at least to me, because [I thought it would be]? > src.conf that's consulted when src is built. So I ran a couple of tests and? > found that it would work in either file HOWEVER if one ports module statement? > was in src.conf and another, different ports module statement was in make.conf,? > that the one in src.conf would get built but the one in make.conf would not.? > > how confusing is that. This is on 11.1-stable. >Make.conf is for building anything that uses make(1) and the build infrastructure in /usr/share/mk. ?Src.conf is for building the freebsd sources only. ?According to build(7), the freebsd sources include /usr/src, /usr/doc, and /usr/ports. ?So settings in both make.conf and src.conf affect ports builds. The difference appears when you use make to build your own software that isn't part of freebsd. ?For that, make.conf settings are applied, but not src.conf. ?At least, that's what the docs say. ?When I look at the .mk files in /usr/share/mk, it appears to me that src.conf gets used even for non-freebsd-source builds. When both files exist, variables set in src.conf will override same- named variables set in make.conf. ?Using VAR += value in both files will accumulate values into VAR rather than replacing them. -- Ian