void/templates
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Custom templates for voidlinux. Probably not ready to be upstreamed, but useful nonetheless.
32 commits 1 branch 0 tags 135 KiB
Shell 100%
Find a file
Marty Oehme f268ba27a8
Add tgpt package
2025-03-16 18:01:33 +01:00
.github Ensure we check out current commit 2025-03-08 17:44:05 +01:00
srcpkgs Add tgpt package 2025-03-16 18:01:33 +01:00
.gitattributes Track xbps files with git lfs 2025-03-06 08:27:40 +01:00
README.md Add tgpt package 2025-03-16 18:01:33 +01:00

README.md

Custom void templates

This is the space for my custom void repo.

It hosts packages that are not yet (or perhaps ever) in the normal void repos, which I've built and maintain for myself.

Use it at your own discretion but I make no promises toward any functionality, stability or non-explody-system-ness.

Currently, files in the repository are only built for x86_64. I would like to extend it to other arches at some point but it is not a priority for me, and I do not know enough about the xbps build system to make it easily possible.

ROADMAP

  • Create new builds for all contained packages
  • Detect changed packages from previous builds
  • build only for those packages
  • serve from custom repository
  • detect upstream changes and update templates
  • build for multiple (appropriate) arches

Package wishlist

  • bemoji

  • ripgrep-all

  • filtile (/src instead of bin)

  • dotter (/src instead of bin)

  • git-bug (/src)

  • bugwarrior - only in pypi for now

  • viddy / hwatch

  • netbird / protonvpn / piactl

  • taskopen

  • dstask

  • tasklite

  • tu

  • https://github.com/nushell/nufmt

  • tgpt

  • impala (iwd TUI)

  • localsend:

    • localsend
    • localsend-cli (localsend-go)

  • gitleaks?

  • syncall - in pypi for now

Auto updating

Goal: auto-update templates on remote updates (checked e.g. every 24h)

  • use renovate to auto-update template file pkgversion

  • open PR for new version

  • For each PR:

    • update checksum for new version
      • grab it from correct place if it is published
      • default to recalculate checksum for new version files
      • auto-commit to PR
    • see if file structure changed?
      • Can't do this here tbh since we need to compare the output of build operation for old and new
    • if checksum OK, automatically commit to main branch

  • on new main addition

  • complete builds

    • only build for new packages?

  • publish new repo version:

    • pull all existing packages in repo into dir
    • put new version of the package into repo
    • repush repo to page with new file