https://github.com/damentz/liquorix-package

Liquorix Debian Package
https://github.com/damentz/liquorix-package

debian-package linux-kernel

Last synced: about 2 months ago
JSON representation

Liquorix Debian Package

• Host: GitHub
• URL: https://github.com/damentz/liquorix-package
• Owner: damentz
• License: gpl-2.0
• Created: 2014-10-09T02:41:50.000Z (almost 10 years ago)
• Default Branch: 6.8/master
• Last Pushed: 2024-04-13T19:00:22.000Z (5 months ago)
• Last Synced: 2024-04-14T05:31:21.616Z (5 months ago)
• Topics: debian-package, linux-kernel
• Language: Python
• Homepage: https://liquorix.net
• Size: 262 MB
• Stars: 272
• Watchers: 14
• Forks: 19
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

• fucking-Awesome-Linux-Software - ![Open-Source Software - Liquorix is a distro kernel replacement built using the best configuration and kernel sources for desktop, multimedia, and gaming workloads. (Custom Linux Kernels / Tools)
• Awesome-Linux-Software - ![Open-Source Software - Liquorix is a distro kernel replacement built using the best configuration and kernel sources for desktop, multimedia, and gaming workloads. (Custom Linux Kernels / Tools)

README

        
# Liquorix Package

[![license](https://img.shields.io/github/license/damentz/liquorix-package.svg)](LICENSE)

This repository contains the Debian package to build Liquorix for both Debian and Ubuntu, and scripts for Debian, Ubuntu, and Arch Linux.

## Prerequisites

The following software must be installed.

1. Docker

2. GnuPG

GnuPG must be configured with a `default-key` line defined in `~/.gnupg/gpg.conf`.  Consult the GnuPG manual for more information if you're unsure what to put here.  But if you're creating a temporary signing key for the purposes of building, follow these steps:

1. Execute `gpg --full-gen-key` and follow prompts

2. Run `gpg --list-secret-keys` to produce a list of keys you own the secrets to

3. Create `~/.gnupg/gpg.conf` and add `default-key EXAMPLE1234...`, where the example is your key from the previous output

## Usage

### Bootstrap Docker Images

Before any builds can be executed, the prepared docker images must be bootstrapped.  To bootstrap all supported images, execute:

```shell

./scripts/debian/docker_bootstrap.sh

```

Subsequent executions of `docker_bootstrap.sh` will update the existing images rather than performing a full build.

### Build Source and Binary Packages

The `debian/docker_build-source.sh` script require two operands, the distribution and release.  For example, to build for Ubuntu Focal, you would execute below:

```shell

./scripts/debian/docker_build-source.sh debian bookworm

```

Once complete, you need to build the binary:

```shell

./scripts/debian/docker_build-binary.sh amd64 debian bookworm

```

If the build completes successfully, the build for Debian Bookworm will be found under `artifacts/debian/bookworm`.

At this time, only AMD64 is supported and is the only architecture that will build successfully.

### Package Signing

If you run into trouble with errors for signing or don't desire signed packages, look for instances in the scripts folder of `dpkg-buildpackage` and add the `--no-sign` flag to all lines.

For example, from the root of this project, execute the following script to find all instances and edit each file as necessary:

```shell

find scripts/ -type f | xargs grep -H 'dpkg-buildpackage'

```

If signing is desired, make sure to update the changelog with `dch -i --auto-nmu` and set the author to match your signing key you set up with GnuPG.

## Contributing

PRs accepted.