Difference between revisions of "VCS package guidelines"

From ArchWiki
Jump to: navigation, search
m (Added Mercurial prototype)
(Mercurial Prototype: - edited prototype to better conform with current prototypes)
Line 55: Line 55:
  
 
<pre>
 
<pre>
# Maintainer: Alias <name@email.org>
+
# Contributor: Name <youremail@domain.com>
  
 +
pkgname=NAME-hg
 
...
 
...
 
source=()
 
source=()
 
md5sums=()
 
md5sums=()
  
_hgroot="http://hg.dillo.org/dillo"
+
_hgroot="HGURL"
_hgrepo="dillo"
+
_hgrepo="MODENAME"
  
 
build() {
 
build() {
 
   cd $srcdir
 
   cd $srcdir
  
   msg "Connecting to $_hgroot"
+
   msg "Connecting to Mercurial server..."
 
   if [ -d $_hgrepo ]; then
 
   if [ -d $_hgrepo ]; then
 
     cd $_hgrepo
 
     cd $_hgrepo
 
     hg pull -u || return 1
 
     hg pull -u || return 1
     msg2 "Finished updating the local repository!"
+
     msg2 "The local files have been updated"
 
   else
 
   else
 
     hg clone $_hgroot $_hgrepo || return 1
 
     hg clone $_hgroot $_hgrepo || return 1
     msg2 "Initial pull complete!"
+
     msg2 "Mercurial checkout done"
 
   fi
 
   fi
  

Revision as of 16:36, 15 December 2009

Template:Article summary start Template:Article summary text Template:Article summary heading Template:I18n entry Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end 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. A Mercurial prototype can be found below.

Guidelines

  • Check for package conflicts. For example fluxbox-svn will conflict with fluxbox. In this case, you need to use Template:Codeline.
  • You should AVOID using Template:Codeline as it generally causes unnecessary problems.
  • Though it is often unnecessary to use the Template:Codeline field when building CVS/SVN/GIT packages (changes to the package are usually often and will be reflected in the Template:Codeline), makepkg will require it.
  • Don't forget to include the appropriate VCS tool (cvs, subversion, git, ...) in Template:Codeline.
  • To preserve the integrity of the checked-out code consider copying the original build directory if you have to make edits. For example, having checked out source code to Template:Filename from Template:Filename you can use:
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).

Mercurial Prototype

# Contributor: Name <youremail@domain.com>

pkgname=NAME-hg
...
source=()
md5sums=()

_hgroot="HGURL"
_hgrepo="MODENAME"

build() {
  cd $srcdir

  msg "Connecting to Mercurial server..."
  if [ -d $_hgrepo ]; then
    cd $_hgrepo
    hg pull -u || return 1
    msg2 "The local files have been updated"
  else
    hg clone $_hgroot $_hgrepo || return 1
    msg2 "Mercurial checkout done"
  fi

...