kreatolinux / src

Kreato Linux source tree

src

Welcome to the Kreato Linux source tree. The source tree includes everything you need to build, test, and maintain Kreato Linux. It includes multiple tools to accomplish this goal. You will find them below.

Build variables

There are a couple of build variables;

• -d:branch: Repository branch that is gonna be used for the default repositories, is set to stable by default
• -d:ver: Specify version manually. Is set to the major version by default.

Projects

kpkg

kpkg is a feature-complete package manager, that is a rewrite of nyaa2. It is written in Nim, and is mainly for use with Kreato Linux.
It is meant to be a much simpler to use package manager compared to the alternatives.
kpkg is heavily inspired by package managers such as kiss, dnf and pacman. Run make kpkg to build.

kreastrap

Kreastrap v3 is a rootfs building utility.
It uses kpkg internally to build Kreato Linux systems.
You can build it by running make kreastrap. The binary will be located on kreastrap/kreastrap.

purr

purr is kpkg's testing utility. You can build it by running make tests. The binary will be located on the usual out folder.

genpkglist

genpkglist is a runfile -> markdown generator. It is used to generate the the package list on the Kreato Linux website.

Build it by running make genpkglist. The binary will be located on the usual out folder.

chkupd

chkupd is a tool to check if a package is up-to-date on a kpkg repository. It also has the ability to attempt to autoupdate the package. You can build it by running make chkupd. The binary will be located on the usual out folder.

jumpstart

Jumpstart is Kreato Linux's new service manager/init system. It is similar in style to systemd. You can build it by running make jumpstart. The binary will be located on the usual out folder.

klinstaller

klinstaller is Kreato Linux's official installer. Unlike other utilities, it is written in sh. It will be available on every Kreato Linux rootfs. you can install it by running make install_klinstaller.

kreaiso

kreaiso is Kreato Linux's ISO image builder. It currently only supports rootfs' that use systemd. More support is coming soon. Build it by running make kreaiso. The binary will be located on kreaiso/kreaiso.

Contributing

Please look at the styling guide before contributing.

License

Licensed under GPLv3. Check LICENSE file for details

src's Issues

Test suite

This should be easy. The test suite should test both internal and external functions.

Multiple packages within the same runfile

gettext and libtextstyle on nyaa-repo could benefit from this.

GPG support

Title says it all.

upgrade: reinstall *if* build succeeds

Right now if build fails then the package gets removed nontheless.

runfile: add test() function

Would be used for running tests of packages.
Example;

test() {
    make tests
}

kpkg update doesnt respect branch info in the config

The updater simply doesn't read the branch info, it looks like

postinstall() on runfile

LD_LIBRARY_PATH export by default

bash-5.1# echo $LD_LIBRARY_PATH

bash-5.1#

exporting LD_LIBRARY_PATH to /usr/lib by default (which the distro uses) can help packages i think. instead of importing the LD_LIBRARY_PATH in package instruction, it should come in default.

kpkg: optional dependencies support

Example;

OPTDEPENDS="test: for wayland support ;; test2: for Xorg support ;; test3: for printing support"

Test utility for built rootfs'

This is crucial for stability. This should be done after kreatolinux/nyaastrap#4 is closed.

Remove flakes

isn't maintained, and only makes my job harder.
Scheduled for v4.3

kpkg not found in builder rootfs

me@machine:~$ docker run -it kreato/builder bash -c kpkg
bash: line 1: kpkg: command not found

kpkg: handle conflicts

planned for v5

kpkg: run ldconfig before and after package installation

kreastrap: rootfs permissions are broken

Rootfs permissions are broken, as a normal user can delete/create files at root.

Major refactor (v5?)

The project currently needs a major refactor.

The reason is I want to stop using include in favor of imports. Doing this will significantly improve the readability of the codebase.

It will also make it so its easier to use as a library.

Use fakeroot for install() on runfile

Is scheduled for src 4.1

Export extra go stuff so it doesnt attempt to use /home/_kpkg

Something like this;

    	export GOENV="/tmp/kpkg/srcdir/go/env" 
    	export GOCACHE="/tmp/kpkg/srcdir/go-build"
	export GOMODCACHE="/tmp/kpkg/srcdir/go-build-mod"
    	go env -w  GOCACHE="/tmp/kpkg/srcdir/go-build"

Or just create a homedir temporarily. I dont know.

kpkg: REPLACES env variable

Pretty self-explanatory.
Example;
REPLACES="ninja"

kpkg: clone repo with sandbox user so it can write to source code

purr: add more independent testing

Right now purr has a static list of dependencies for the dependency test, and that fails when we update the package on the repo.
It would be nice if purr has some kind of dependency handler, that is spesific to itself so it can compare both results.

Include installer in rootfs

Make autocd more stable

Sometimes it just doesnt work or cds into the wrong folder.

kpkg hangs sometimes while installing

Only happens when multithreading is enabled.
No idea why.

Be less dependent on shell commands

One of the biggest issues on nyaa3 currently is it is using too much shell commands to function. Shell commands are expected to be used, since building will require some commands here and there, but there is excessive use of them.

Things that can be done to partially fix this issue

• Make a wrapper for libgit2 (projects do exist that wrap libgit2 but they are unmaintained and/or doesn't work anymore)
• Make a wrapper for libarchive
• Rewrite modules/removeInternal.nim Done

Write a nim-based container solution for kpkg

Title says it all.

Something like Docker that can be integrated in kpkg without shell commands, and hopefully doesn't have much dependencies.

We could also make it a standalone tool just for fun!

downloader: pretty progress bars

I have no idea as to do this, but i should do it someday.

dephandler: add the ability to detect circular dependencies

kreastrap: remove buildPackages function

Now handled by chkupd in a better way, since it autoupdates and uses containers to build packages.

kreastrap: add the ability to generate ISOs

We need to have an ISO so users can install Kreato Linux without having to use external Linux distributions.

add ALTERNATIVE_TO environment variable for runfiles

This is for alternative support.

-r option doesn't work

Test it with

mkdir test
nyaa update
nyaa build neofetch -r=./test

kpkg: a proper debug mode

Have a proper debug mode that shows every single detail there is.

LICENSE variable

Would work like this;
LICENSE="GPL LGPL"
Doing so will copy said licenses on /usr/share/licenses/PACKAGENAME/COPYING

runfile: NOCHKUPD variable

NOCHKUPD variable would be used for the packages that don't want to get autoupdated by chkupd. This will not disable chkupd compiling the package.

NOCHKUPD="y" to enable.

kpkg: multiple build types for packages

Something like package_PACKAGENAME but for builds.
Example: build_grub-efi()

kpkg: version dependencies

Have dependency handler support version checking.
Example;

DEPENDS="kpkg>=4.2.0"

kpkg: have the ability to use multiple binrepos

Title says it all.

Jumpstart opens even though it isn't pid1

Title says it all.

Implement sandboxing

At the very least we shouldn't build as root. This has major security issues.
I am thinking of a _nyaa user that is used to build the package for now.
We could always use something like bubblewrap to have further sandboxing later.

parallel downloads

would be nice to have.

chkupd: be independent of Docker

Docker is nice and cool, but using our own container solution to do the job will be more efficient, cleaner, and more debuggable.

chkupd: failed package build logs

Title says it all.

The ability to git clone for a source

Example;

SOURCES="git::https://github.com/kreatolinux/nyaa3::45821072d9513a9df1031f0495214e1a1ab6f903"

kpkg: implement service packages

Scheduled for v5.2.

See kreatolinux/kpkg-repo#70

Building packages with GitHub Actions

This will be made with a self-hosted runner of course, unlike building rootfs.
This will increase transparency as how packages are built, and logs of them would be publicly available.
Also would automate a lot of tasks that are manually done right now, lowering required maintenance.

(Currently set to be done at nyaastrap v3.1.0)

kpkg: handle local files in SOURCES

kpkg: rewrite upgradecmd

kpkg: centralized place for source code

Like /var/cache/kpkg/archives, but for source code instead of binaries.
This will make rebuilds easier since the source tarball doesn't need to be redownloaded.

kpkg: remove whitespace from SOURCES while reading it

Title says it all.