Here are all the AUR packages maintained by me ;)
The equivalent AUR search is:
https://aur.archlinux.org/packages/?SeB=M&K=ItachiSan
Are you a comaintainer and want to start quickly to hack stuff? Then here is what you should do.
(I assume here we already talked about stuff & I checked that you actually know what we are talking about ;) )
Before hacking the packages, you need to get some stuff right:
-
Fetch this repository via:
git clone https://github.com/ItachiSan/linux_packaging.git /path/to/my_local_copy
-
Update the submodules:
git submodule update --init
If you want to work on a specific submodule or a set, just provide it as parameted:
# Set up only the po-debconf submodule git submodule update --init po-debconf # Set up only the telegram-destkop submodules git submodule update --init telegram-desktop*
-
Install the provided Git hooks with:
./hooks/install.sh
These are required for correctly generating the commits.
Just run the tool:
./tools/check_updates.sh
You should have a private Github access token to guarantee consistent API calls, see the consideration here.
Now you are practically ready to go: if you want to update the packages, the way is simple:
-
Enter the package folder
-
Edit the PKGBUILD with any editor you like.
IMPORTANT: packaging-only changes increase only the
pkgrel
, only upstream version changes increasepkgver
. -
updpkgsums
-
Build the package, to verify all is working
-
Commit the changes; the message will be initially formatted with the repository standard. Just add the list of changes with a list, for example:
# This is already here updpkg: APACKAGE 1.2.3-4 # Then you add lines like: - Version bump. - Improvements to PKGBUILD. - ...
The list should mention all the actual changes.
- Automated packaging
- Distribution via Github Pages; right now I have an OpenBuildService repository, but ugh.
- Add more packages (requires 1. & 2. properly working)