do not name your package gish-hb if there are existing packages called aquaria-hib, crayonphysicsdeluxe-hib and uplink-hib. Try to use established naming conventions, e.g. If the packaging of some program requires more effort and hacks than buying and using the original version, do the simplest thing-it is Arch!īefore naming a package, search the AUR for existing packages of software that you are packaging. Using open source engines together with the original game assets gives users access to bug fixes and eliminates several issues caused by binary packages. Many commercial games ( some are listed in this Wiki) have open source engines and many old games can be played with emulators such as ScummVM.

It is better to support software that can be fixed if just one person out of millions cares enough.

It is better to support software that is actively maintained.

It is better to support software that is owned by us all than software that is owned by a company.

Yes, it is better to leave this guide and spend some time searching (or maybe even creating) alternatives to an application you wanted to package because:

Common rules Avoid nonfree software when possible It is simpler to apply tweaks, fix bugs and seek/provide help in a single public place like the AUR versus submitting patches to proprietary developers who may have ceased support or asking vague questions on general purpose forums. The ability to track state, perform automatic updates of any installed piece of software, determine ownership of every single file, and store compressed packages in a well-organized cache is what makes GNU/Linux distributions so powerful. # cp filename /usr/bin/ you can just issue $ makepkg -i Most non-free applications are obviously much more complicated, but the burden of downloading an archive/installer from a homepage (often full of advertising), unpacking/decrypting it, hand-writing stereotypical launcher scripts and doing other similar tasks can be effectively lightened by a well-written packaging script. This is applicable even to the simplest of applications, which consist of a single script to be installed into /usr/bin. Simplification of installation/removal process.There are multiple reasons for packaging even non-packageable software: Note: All information here is package-agnostic, for information specific to the most typical nonfree software see Wine PKGBUILD guidelines.

Nullsoft sfx installer unpacking