Difference between revisions of "VCS package guidelines"

From ArchWiki
Jump to: navigation, search
(clean-up)
m (fixed what I caused)
Line 6: Line 6:
 
{{i18n entry|English|VCS PKGBUILD guidelines}}
 
{{i18n entry|English|VCS PKGBUILD guidelines}}
 
{{Article summary heading|Related articles}}
 
{{Article summary heading|Related articles}}
{{Article summary wiki|ABS - The Arch Build System}}
+
{{Article summary wiki|Arch Build System}}
 
{{Article summary wiki|Building Packages in Arch Linux}}
 
{{Article summary wiki|Building Packages in Arch Linux}}
 
{{Article summary wiki|Arch Linux User-Community Repository (AUR)}}
 
{{Article summary wiki|Arch Linux User-Community Repository (AUR)}}

Revision as of 20:17, 30 November 2009

Summary help replacing me
Creating PKGBUILDs for software managed with version control systems.
Available in languages

Template:I18n entry

Related articles
Arch Build System
Building Packages in Arch Linux
Arch Linux User-Community Repository (AUR)
makepkg
pacman
PKGBUILD Tricks
PKGBUILD Variables

Guidelines for creating PKGBUILDs for software managed with version control systems.

Prototypes

The Template:Package Official package provides prototypes for cvs, svn, git and darcs PKGBUILDs. When abs is installed, you can find them in Template:Filename.

Guidelines

mkdir src/$_cvsmod-build

cd src/$_cvsmod-build
../$_cvsmod/configure

or:

cp -r src/$_cvsmod src/$_cvsmod-build
cd src/$_cvsmod-build
  • With the introduction of the AUR, it is most important to avoid using backtick execution to create package variables. makepkg will automatically bump the Template:Codeline anyway when building the package (unless Template:Codeline is used).