You are not logged in.
While AUR 4 is down at the moment, I have a couple of questions related to the new Git based system. These may all be answered when the site's back up and I can peek at some samples on there, but I assume there is no way to add non-packaged files to Git version control on AUR 4, is there? I use a couple of scripts to essentially test/sandbox my package before I submit, but those scripts should never be packaged.
Currently, I use a Github repo to host my build files so others can fork and submit merge requests, and in the repo I manage these test scripts with separate folders so they never clutter the actual source package files. I'm not sure if AUR4 supports "build only" files/folders, or if they would need to be maintained outside of AUR?
It would be great if I only have to deal with the one Git AUR4 repo, which brings up my next question: can others fork and submit merge requests to the maintainer on AUR4?
Last edited by twelveeighty (2015-06-03 02:47:02)
Offline
The way to do this with git would be separate branches. Reserve the master branch for just AUR files and commit all of your "build only" files in a different one. Whenever you want to test your PKGBUILD, just merge master into your build branch.
Offline
The way to do this with git would be separate branches. Reserve the master branch for just AUR files and commit all of your "build only" files in a different one. Whenever you want to test your PKGBUILD, just merge master into your build branch.
You don't have to merge, git provides a script called git-new-workdir. You can use it to checkout the build branch in a new working directory.
# create normal repository
mkcd /tmp/testgit
git init
touch README
# ignore the directory where we will put the build branch
echo "build/" >.gitignore
git add .
git commit -m "init master"
# create the build branch
git checkout --orphan build-tools
git rm -rf .
touch buildscript
git add .
git commit -m "init build branch"
# go back to master
git checkout master
# open the build branch in a new workdir (the subdir we prepared in gitignore)
git new-workdir . build build-tools
cd buildEdit: You can also use your github repository as your master location. When you have a new release, merge it into the master branch in the AUR remote without the build directory.
git remote add <the-aur-remote>
git checkout aur/master
git merge --no-commit -no-ff origin/master
git reset HEAD <build_directory>
git commit -m "merged origin/master"Last edited by progandy (2015-06-02 21:52:53)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
How will my AUR4 RSA key be known to the system so I can reupload my packages?
Offline
How will my AUR4 RSA key be known to the system so I can reupload my packages?
When the AUR4 site goes live on the 8th, you will be able to add your public key to your AUR account after you log in.
EDIT: this is explained here: https://wiki.archlinux.org/index.php/Ar … hlinux.org
Last edited by WorMzy (2015-06-02 22:52:16)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Cool - thanks for the tips, I'll mark as [solved].
Offline