Packagers wanted!

14 April 2018, 23:22:55

We urgently need more people able to contribute to packaging.

You don't have to be an expert in the occult arts for that; an elementary grasp of Linux in general and how PKGBUILD works should be enough for basic contributions. Help and training will be provided, free of charge!

Re: Packagers wanted!

Hey man I just made my first 3 PKGBUILD's, I made them out of git repos instead of them being like actual packages with version numbers/etc, all I really need to learn is how to give it a version number & how to make it automate its own updates...

like... when there's a new package available to be packaged, how do we know? Do the packages just update themselves or do we need to alter the PKGBUILD to make it update in the package manager? I can start with gaming emulators, I have so far done Dolphin-emu, Citra-emu & Medusa-emu, once I am more experienced I'll be able to do other packages. Maybe in a few months I'll have enough experience to do more packages but I would prefer to start with stuff that requires cmake, qmake or ./configure

Inbox me if you don't mind & just teach me a few of the things I have mentioned here that I don't understand & I'll be good-to-go for the simple packages, and you guys can look over the first ones I make to make sure I am doing everything right & give me tips about what I am doing wrong. This is the first one I made, I made a similar one for citra-emu & medusa-emu.

Re: Packagers wanted!

@kenny_w Be aware that git packages belong to AUR only and should have "-git" suffix in the package name.these git packages are mostly used to test new features..."-git" pgkbuilds are updated only when there is something wrong with current pkgbuild or when there was change in buildsystem...these pkgbuilds can stay unchanged for years and when building always offer newest version.git pkgbuilds usually have "version" function, so when you build them the version is set to current one.

Normal PKGBUILDS used in our repositories are downloading specific version of desired program,PKGBUILD is updated when the new release is made or when there is some error with pkgbuild.

PKGBUILD which you posted is mixture of these, it is good for personal use but nightmare for others.- downloads source from git (build is not stable, you cant offer stable package)- Package name should reflect that the source is from git with "-git" suffix- Package version should specify program version (in case of "-git" package provide "version" function)- Make things easy to read (dont mix tabs and spaces, indent body of functions)- Long lines are hard to read, if you can cut long line to multiple short lines

These are my thoughts regarding this subject, i might also be totally wrong .