| Git Clone URL: | https://aur.archlinux.org/st-git.git (read-only, click to copy) |
|---|---|
| Package Base: | st-git |
| Description: | A simple virtual terminal emulator for X. |
| Upstream URL: | https://st.suckless.org |
| Licenses: | MIT |
| Conflicts: | st |
| Provides: | st |
| Submitter: | vesath |
| Maintainer: | Farzat |
| Last Packager: | Farzat |
| Votes: | 50 |
| Popularity: | 0.020914 |
| First Submitted: | 2012-11-30 01:40 (UTC) |
| Last Updated: | 2024-01-22 11:26 (UTC) |
echo 'Applying patches from $_startdir if they exist...'
This is not going to print $_startdir value. Either replace single quotes by double quotes or concatenate the variable value between the literal string 'Applying patches from '"$_startdir"' if they exist...'
patch -p1 -s -i "$patch"
This is not going to apply any patch, you need to pass the path where the source code is patch -d "$_sourcedir" -p1 -s -i "$patch"
@galunid
Thank you, fixed.
if [ -d "$_startdir}/patches" ]; then
it has unnecessary "}", thus prevents your PKGBUILD from applying patches
@shoober420 cool, thanks. Just a heads up: _gitname, _sourcedir, and _gitdir all store the same information. _gitdir is just a variable I created to store the contents of the pkgname variable with "-git" removed. This is just what I use for git pkgbuilds that have a similar name.
Alternatively you could do away with these variables and tell git to download the project into a directory with the same name as the pkgname with this modification to the source variable
source=($pkgname::git://git.suckless.org/st
@Static_Rocket Updated and added you to the list of contributors, thank you.
Alright, well I've made some changes since then. This one is a little cleaner than the one I originally linked: http://ix.io/2mFg
(Mind throwing my name in there somewhere?)
Whoops, I uploaded your patch @Static_Rocket. I myself would include the scrollback patch as optional, but it has broke compiling for me in the past.
Updated, sorry for the wait.
@shoober420 I would be honored but I'm not entirely sure the autopatcher is actually useful for a git based package. As the git package grabs the source, the new patches must be fetched manually and have a higher likelihood of breaking. I thought about using the reset in the prepare to keep it locked to a user specified version but then this would make the pkgver script wrong and defeat the purpose of syncing with the git source. I was just goofing around and didn't feel like patching it manually when I was testing.
Pinned Comments