Re: Contributing the build of a KVM image

From: Jo Durchholz <jo_at_durchholz.org>
Date: Sat, 10 Feb 2024 23:58:55 UTC
Hi Pete, hi all,

thanks for the info!

Onwards to the next question:
What would be the right place to ask questions about how to run `make`?

In case this is already the right place, here they are:

1) I'm worried that make will write files to directories that I'm not 
aware of, or even overwrite stuff it has no business overwriting.
How to I make sure that it does not write anywhere except 
~/projects/freebsd (which is the place where I want to experiment with 
the freebsd build)?

2) I want to build the Vmware Vagrant file and its dependencies; what 
would the correct make target be? (I tried to figure it out but gave up 
when I saw it's include files; I don't know what to look for when 
figuring out from where they might be called.)

3) I need to run make on a Linux box. I'm aware of make.py; is there 
anything specific I need to consider when building Vagrant files?
In particular, I'm vaguely worried that something inside the Makefiles 
will want to install FreeBSD binaries, which would fail but I'm not sure 
how much damage a failing build process might do? (Probably nothing, but 
since the Vagrant stuff is in a "release" directory, this might be a 
less well tested part of the build process, so better ask rather than be 
sorry.)

Regards,
Jo

On 30.01.24 01:28, Pete Wright wrote:
> 
> On 1/29/24 14:41, Jo Durchholz wrote:
>> Hi all,
>>
>> where do I turn to if I want to contribute to the FreeBSD 
>> build/release process so that a KVM image will be built?
>>
>> This is not actually about virtualization per se but about the 
>> build&release process, so I guess I'd be wrong here.
> 
> 
> I'd suggest filing a bug first, along with a patch if you have one:
> https://bugs.freebsd.org/bugzilla/
> 
> depending on the complexity of changes developers may ask for you to 
> start a review in phabricator:
> https://wiki.freebsd.org/Phabricator
> 
> if you'd like to get more eyes on this it may be worth sending a message 
> to freebsd-hackers@ or freebsd-current@
> 
> 
> -pete
>