CCF_100
/
PKGBUILDS
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
100 Commits
1 Branch
0 Tags
210 KiB
Shell 100%
 
Go to file
Tk-Glitch 07ffc97f85 Sync 
> linux-tkg: linux54-tkg: 5.4.44
  > linux-tkg: linux56-tkg: 5.6.16
  > wine-tkg-git: Hotfixer: Disable LAA and protonify patchsets when the user refuses hotfixes
  > wine-tkg-git: Import rebased b658ec5971 to proton-sdl-joy-2 patchset
  > wine-tkg-git: Proton-tkg: Set _hotfixes_no_confirm by default.
  > wine-tkg-git: Proton-tkg: Add PROTON_NO_WRITE_WATCH entry to user_settings.py
  > wine-tkg-git: Initial sync with Proton 5.0-8 RC
  > wine-tkg-git: Silence hotfixer warning on mainline
  > wine-tkg-git: Nuke reportedly problematic hunks from proton-winevulkan patchsets
  > wine-tkg-git: Hotfixer: Robustness enhancements and fixes  - Introduce the "earlyhotfixer" script, that gets loaded at the time we previously loaded the "normal" hotfixer  - Move early checks (community patches and broken staging upstream commit hotfixing) to "earlyhotfixer" and remove the "early" userpatching from prepare  - Load the hotfixer right before the nonuser_reverter checks, so our sources are correctly checked out ready for reverting work (it was running too early before, leading to potential breakage on legacy)  - Run the hotfixer after the nonuser_reverter so we don't end up with conflicts preventing git to do its job  - Don't set _broken_staging_44d1a45_localreverts="true" unconditionally if esync or fsync is disabled  - Replace the _patches variable by a separate _hotfixes one to contain our hotfixes array. This prevents a potential conflict with userpatches  - Check for the oldest hotfix-needy commit before prompting the user about hotfixes  - Remove unneeded fluff
  > wine-tkg-git: Update wine-tkg patch (mainline) for c7760ce, and move previous version to legacy.
 		2020-06-03 19:42:57 +07:00
amdgpu-pro-vulkan-only@c92103131a New frog? New frog! Thanks @gardotd426 2020-04-17 19:14:52 +07:00
amdvlk-opt@dc3e527080 Sync 2020-05-30 12:28:47 +07:00
community-patches@33cdd5a86d Sync 2020-06-03 02:34:34 +07:00
dxvk-tools@8871b83dc5 Sync 2020-05-13 08:48:06 +07:00
faudio-git@9b28fc3dbb Sync 2020-06-03 02:34:34 +07:00
gamescope-git@4994740755 Sync 2020-06-03 02:34:34 +07:00
gst-libav@2770741f68 Sync 2020-04-01 21:19:07 +07:00
linux-tkg@a644d088f2 Sync 2020-06-03 19:42:57 +07:00
llvm-git@ac013975f5 Sync 2020-06-03 02:34:34 +07:00
mesa-git@a6aabff017 Sync 2020-06-03 02:34:34 +07:00
mingw-on-arch-automator@25b159cf32 Sync 2020-05-18 16:23:14 +07:00
mostlyportable-gcc@96238ba3da Sync 2020-05-24 16:21:16 +07:00
nvidia-all@f1f5f0f6c1 Sync 2020-06-02 15:25:27 +07:00
spirv-tools-git@945e71f72a Sync 2020-06-03 02:34:34 +07:00
vkd3d-git@23f67003f4 Sync 2020-06-03 02:34:34 +07:00
vulkan-headers-git@5086ae91ed Sync 2020-06-03 02:34:34 +07:00
vulkan-icd-loader-git@aa8db77466 Sync 2020-06-03 02:34:34 +07:00
wine-tkg-git@50bb95bb17 Sync 2020-06-03 19:42:57 +07:00
.gitmodules Switch amdvlk-opt submodule url to https. Sorry about that 🐸 2020-05-21 19:19:22 +07:00
README.md readme: Add a note about the TkgThingy script. 2020-05-18 16:21:27 +07:00
TkgThingy TkgThingy: Create ext config dir if needed 2020-04-19 21:00:22 +07:00

README.md

PKGBUILDS and other scripts made for random people & frogs

Thanks to Kassin for the meme-worthy banner

How-to use that mess :

While some of the scripts might work fine on any distro, the PKGBUILDs will only work on distros with access to pacman and makepkg.

If you need to access pacman and makepkg outside of Arch-linux and distros based on it (like Antergos or Manjaro), you can "hijack" your current distro with Bedrock Linux at your own risk: https://bedrocklinux.org

  • Clone the whole thing (that enables you to use git submodule update --remote to get updates) :
git clone --recurse-submodules https://github.com/Tk-Glitch/PKGBUILDS.git

From the directory of the package you want to build (where the PKGBUILD is located), run

makepkg -si

That will grab the required dependencies, build, then install the newly created package(s).

  • For bash scripts, just run them from their respective directory - You might find additional details in the readme dedicated to the tool you want to build.

  • For your convenience, a script is available in the root of PKGBUILDS to pull updates and create external configuration files easily: ./TkgThingy

Why aren't the PKGBUILDs on AUR ?! :

While some are already available there without userpatches or lib32 support, the most interesting ones aren't (namely linux kernels, nvidia-all and wine-tkg-git) because of the way they are working. You're prompted for options or even config file editing to get the package customized the way you want it to be. For nvidia-all, there's no way around it so I'd consider that non-AUR compliant by default. For linux kernels and wine-tkg-git, I could indeed provide a fixed preset and remove all prompts. That would work. But then, are these still as interesting without customization? I strongly believe they aren't.

Daily builds (pacman packages) for most packages are available on chaotic-aur (https://wiki.archlinux.org/index.php/Unofficial_user_repositories#chaotic-aur):

Wanna talk about it? Need help? Feel free to join the Frogging Family discord server : https://discord.gg/jRy3Nxk

If you like my work, consider visiting my patreon page : https://www.patreon.com/tkglitch

Thanks to gardotd426, Gabe E, Vitalwonhyo, Glorious Eggroll, Hans-Kristian, Anisan, Jonny Teronni, Zs. Cs. Sz., JudgeVanadium, Lutris, Oli, Fábio, Bill, Kristoffer, Typhoon, Ole Erik, Stephan, contributors, and all anonymous Patrons, supporters and curious minds! You're giving driving energy and purpose to my work. Much frog love to all of you guys <3

You can also donate to me via https://www.paypal.me/TkGlitch