index | | raw e-mail
-------- Original Message -------- On Thursday, 03/26/26 at 22:22 Mark Millard <marklmi@yahoo.com> wrote: On 3/26/26 04:30, polyduekes@proton.me wrote: > On Thursday, March 26th, 2026 at 3:26 AM, Lexi Winter <ivy@freebsd.org> w= rote: > >> polyduekes@proton.me wrote in <m-cS1PTzow3fGVjDOpYyn6W_o4S1wWeW_rAts1LiW= Rgqkb4CXug6y8weHusL07G9vt2l5WGX76OF2C-JckHufUvwSqJ4511_3wNZ81QeOz4=3D@proto= n.me>: >>> is needing to do both buildworld and buildkernel to create a pkg repo >>> the intended behaviour or is that planned to change >> >> right now i don't believe there are any plans to change that. i suppose >> it might change in the future. usually people want to build both the >> world and the kernel, so this isn't an oft-requested feature. >> >> could you elaborate on why you want to build world but not kernel? >> this would help inform development efforts in that area. >> > i usually make my own changes to base code to test some things and learn = a few others,and most of the time the changes i make touch only world and d= ont touch kernel at all,so i like to avoid unnecessary compilation of the b= inaries and things i didn't change and doing only make buildworld and not m= ake buildkernel buildworld is part of that reason Are you aware of META_MODE for buildworld and buildkernel (with its use of filemon.ko)? Its purpose is to keep track of things and so generally rebuild what is necessary but avoid rebuilding what is not. For example, back to back rebuilds have the second one not taking very long based on the lack of changes. >>> additionally may i ask why it's recommended to do 'make >>> upodate-packages' over 'make packages' >> >> 'update-packages' will copy unchanged packages from the previous build >> to the current build, which means if only a small number of packages >> have changed, the system won't try to update every package. >> > > -- =3D=3D=3D Mark Millard marklmi at yahoo.comhome | help