An experimental kiss repo for FreeBSD.
The installation currently requires you to hijack an already existing FreeBSD installation. This will change in the future.
On the FreeBSD machine (and as root), install git with pkg:
# Install git, since it pulls in curl.
yes | pkg install git
git clone https://github.com/ehawkvu/fbsd-repo
git clone https://github.com/kiss-community/kiss
# Setup our environment for kiss.
export KISS_SU=sudo
export MAKEFLAGS="$(sysctl -n hw.ncpu)"
export PATH="$PATH:$PWD/kiss"
export KISS_PATH="$PWD/fbsd-repo/core"
export KISS_HOOK="$PWD/fbsd-repo/hook"
# Download everything now, since we won't have curl in a moment.
kiss d bsd-base curl git gmake kiss libretls
# Update certdata so our curl works
sh $PWD/fbsd-repo/libretls/files/update-certdata.sh
# Remove stuff from pkg.
rm -Rf /var/db/pkg/*
rm -Rf /usr/local/*
# Build and install core/ except for bsd-base.
kiss b curl gmake git kiss libretls
kiss i curl gmake git kiss libretls
# Do NOT install this package yet, there's still plenty of
# issues with it (see below).
# You're welcome to build it, however.
kiss b bsd-base
# If you *really* want to install bsd-base, you first have
# to remove the immutability flag from any file on the system,
# else suffer an actually failed install.
# Yes I know this seems wrong, but FreeBSD doesn't seem to mind :)
chflags -R noschg /
# To actually install the package, follow the steps in the section
# below to patch the kiss package manager, so that any installation
# will work (add `|| true` after the appropriate cp calls).
# Once that's done you can run:
kiss i bsd-baseWith the above steps taken, the rootfs can be generated, however there is a manual step that you will have to perform, as noted below.
Currently kiss can build bsd-base just fine, however it cannot install it as of yet.
Installation of bsd-base required the cp calls in pkg_install() in kiss to be followed by || true just so that installation could finish successfully. There are many symlinks that just fail to install properly with this particular package, here's the errors:
cp: symlink: ../sbin/mailwrapper: File exists
cp: symlink: ../sbin/mailwrapper: File exists
cp: symlink: ../usr/sbin/nologin: File exists
cp: symlink: ../../bin/grep: File exists
cp: symlink: ../../bin/pkill: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/lib/./include with non-directory /root/.cache/kiss/proc/50870/extract/bsd-base/usr/lib/include
cp: symlink: ../../libexec/ld-elf.so.1: File exists
cp: symlink: ../../libexec/ld-elf32.so.1: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/share/nls/./POSIX with non-directory /root/.cache/kiss/proc/50870/extract/bsd-base/usr/share/nls/POSIX
cp: cannot overwrite directory /tmp/rootfs/usr/share/nls/./en_US_ASCII with non-directory /root/.cache/kiss/proc/50870/extract/bsd-base/usr/share/nls/en_US.US_ASCII
cp: symlink ../local/tests: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/test/sys/pjdfstest/./tests with non-directory /root/.cahe/kiss/proc/50870/extract/bsd-base/usr/tests/pjdfs/tests
cp: symlink: ../sbin/mailwrapper: File exists
cp: symlink: ../sbin/mailwrapper: File exists
cp: symlink: ../usr/sbin/nologin: File exists
cp: symlink: ../../bin/pgrep: File exists
cp: symlink: ../../bin/pkill: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/lib/./include with non-directory /root/.cache/kiss/proc/50870/extract/bsd-base/usr/lib/include
cp: symlink: ../../libexec/ld-elf.so.1: File exists
cp: symlink: ../../libexec/ld-elf32.so.1: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/share/nls/./POSIX with non-directory /root/.cache/kiss/proc/50870/extract/bsd-base/usr/share/nls/POSIX
cp: cannot overwrite directory /tmp/rootfs/usr/share/nls/./en_US_ASCII with non-directory /root/.cache/kiss/proc/50870/extract/bsd-base/usr/share/nls/en_US.US_ASCII
cp: symlink: ../local/tests: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/test/sys/pjdfstest/./tests with non-directory /root/.cahe/kiss/proc/50870/extract/bsd-base/usr/tests/pjdfs/tests
Yes the repeat lines did occur in the actual output. This is the exact log. No, I don't know what caused it.
Update:
Just ran a build with the new bsd-base package. Here are the remaining errors:
cp: cannot overwrite directory /tmp/rootfs/usr/lib/./include with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/lib/include
cp: cannot overwrite directory /tmp/rootfs/usr/share/nls/./POSIX with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/share/nls/POSIX
cp: cannot overwrite direcotry /tmp/rootfs/usr/share/nls/./en_US.US_ASCII with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/share/nls/en_US.US_ASCII
cp: symlink: ../local/tests: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/tests/sys/pjdfstest/./tests with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/test/sys/pjdfstest/tests
cp: cannot overwrite directory /tmp/rootfs/usr/lib/./include with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/lib/include
cp: cannot overwrite directory /tmp/rootfs/usr/share/nls/./POSIX with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/share/nls/POSIX
cp: cannot overwrite direcotry /tmp/rootfs/usr/share/nls/./en_US.US_ASCII with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/share/nls/en_US.US_ASCII
cp: symlink: ../local/tests: File exists
cp: cannot overwrite directory /tmp/rootfs/usr/tests/sys/pjdfstest/./tests with non-directory /root/.cache/kiss/proc/66486/extract/bsd-base/usr/test/sys/pjdfstest/tests
Much more manageable!
Update:
I haven't been able to resolve the above issue yet, however I think ti should be pretty
easy to fix with an additional post-build hook. I'd like to have something automatic,
but I'd settle for a couple of rm's.
Update:
The package now installs without errors! You no longer need to do the hacky || true in kiss!
First, enable the 'core' and 'fake' repositories, as it provides packages that satisfy dependencies.
export KISS_PATH="/path/to/fbsd-repo/core"
export KISS_PATH="$KISS_PATH:/path/to/fbsd-repo/fake"
Once done, you can then append 'extra':
export KISS_PATH="$KISS_PATH:/path/to/fbsd-repo/extra"
If you want to stay on the same release for it's entire cycle, its possible
to modify the bsd-base package to use the snapshot links of the STABLE
branch. For example, to update to the latest snapshot release of 13.1, edit
bsd-base/source to contain the following:
https://download.freebsd.org/snapshots/amd64/13.1-STABLE/src.txz
The releases are in bsd-base mainly to keep big updates at a minimum since
building bsd-base is quite a process, since it is the entire system.
- Use a git module for the upstream kiss repository, so less maintenance is required.
- Generate a rootfs
- Make sure you can perform an installation via rootfs (& add docs on how to)