local opnsense git question

Started by none, April 07, 2025, 11:28:35 PM

Previous topic - Next topic
Hi,

I am trying to build ARM64 images for opnsense and now I have to add manually two files after I dd the image to the microSD.

I found a small guide for git on this post, but the images won't have the same files I commit using this commands.

I use the following line to build:

make -C /usr/tools/ VERSION=$TAG_SRC DEVICE=$DEVICE base

Where TAG_SRC on the last build has the value of 25.1.4.

I did:

git tag -f -m "message" 25.1.4

and then on the /usr/core (where my commited files are) I run:

git checkout 25.1.4

and there my files are what I expect them to be.

My knowledge of git is not much, if anyone has any hints here :)

I want to include my fingerprint for the packages and a new /usr/local/etc/rc script for ARM64 gpart resizing.

Thanks in advance :)

none
"We will call you Cygnus,
the God of balance you shall be."

The problem with faking modifications (force-pusing tags) is that it becomes untraceable. I would recommend using a copy of config/25.1 and/or setting COREBRANCH=stable/25.1.4-mine-or-other-name and checking out that branch based on a particular tag or stable/25.1:

# cd /usr/core && git checkout -b stable/25.1.4-mine-or-other-name origin/25.1.4

That will make all build targets in tools.git align to your local modifications.

For the sake of building open source software the build will try to cling to actual commits because that is the only way to make a build fully reproducible and more trustworthy.


Cheers,
Franco