Skip to content

Tatsh/tatsh-overlay

Folders and files

NameName
Last commit message
Last commit date
Jan 26, 2025
Feb 4, 2025
Jul 10, 2023
Jul 10, 2023
Dec 9, 2023
Jan 23, 2025
Feb 3, 2025
Jan 23, 2025
Feb 4, 2025
Feb 4, 2025
Jan 26, 2025
Jan 13, 2023
Dec 16, 2024
Sep 20, 2024
Dec 17, 2024
Dec 10, 2024
Aug 25, 2024
Feb 4, 2025
Feb 4, 2025
May 13, 2024
Feb 9, 2025
Dec 30, 2024
Sep 9, 2023
Feb 3, 2025
Nov 24, 2024
May 6, 2024
Jan 8, 2024
Apr 22, 2024
Feb 4, 2025
Dec 9, 2024
Oct 14, 2024
Jan 23, 2025
Jun 29, 2024
Dec 16, 2024
Apr 14, 2024
Feb 4, 2025
Dec 30, 2024
Feb 4, 2025
Sep 16, 2024
Feb 4, 2025
Jun 21, 2023
Jan 23, 2025
Sep 16, 2024
Jan 23, 2025
Dec 30, 2024
Feb 25, 2024
Sep 9, 2023
Jan 23, 2025
Feb 4, 2025
May 22, 2024
Dec 1, 2024
Aug 4, 2024
Feb 9, 2024
Dec 16, 2024
Nov 3, 2024
Mar 12, 2024
Feb 9, 2025
Oct 14, 2024
Jul 16, 2023
Feb 4, 2025
Dec 30, 2024
Dec 10, 2024
May 6, 2024
Nov 3, 2024
Nov 23, 2023
Sep 9, 2023
Jun 17, 2023
Jan 2, 2022
Sep 18, 2024
Jul 3, 2023
Jan 29, 2021
Feb 10, 2025
Feb 10, 2025
Feb 10, 2025
Feb 10, 2025

Repository files navigation

tatsh-overlay

QA

This is stuff I make randomly. Usually updated every Sunday after 9 AM EST.

If you find a bug, please file an issue.

Installation

emerge app-eselect/eselect-repository
eselect repository enable tatsh-overlay
emerge --sync

Only unmask packages you use from this repository

Based on Masking installed but unsafe ebuild repositories.

In /etc/portage/package.mask/tatsh-overlay, block all packages from this repository by default:

*/*::tatsh-overlay

In /etc/portage/package.unmask/tatsh-overlay, allow packages from this repository:

games-arcade/stepmania::tatsh-overlay

Contributing

New packages are unlikely to be accepted unless they are related to emulators, reverse engineering, etc. Wine-wrapper packages will not be accepted. Binary packages are only accepted if there is no alternative.

For binary packages without source available, do not add the -bin suffix to the package name. If providing a binary package that is unreasonable to build in the Portage environment for the time being, add the -bin suffix to indicate so.

Please make a fork and a new branch, make your changes and then run the following steps:

  1. ebuild [name of ebuild] manifest clean install

    If testing runtime is important (anything that is not a library), please also add merge to the above command and run some basic checks. For instance, with an emulator run a game that is known to be working in the official build.

  2. yarn && yarn qa

    (Requires Node.js and Yarn to be installed.)

    Make sure the above passes completely.

  3. pkgdev commit --signoff and fill in the required message if requested (do not change or remove the prefix). Even if not requested, add to the commit message as necessary.