Difference between revisions of "VCS package guidelines"

From ArchWiki
Jump to: navigation, search
m (moved Arch CVS & SVN PKGBUILD guidelines to VCS PKGBUILD guidelines: This page is not specific to cvs and svn...)
m (Tips: - Ellipsis: A three-dot symbol used to show an incomplete statement. :))
(48 intermediate revisions by 23 users not shown)
Line 1: Line 1:
[[Category:Package management (English)]]
+
[[Category:Package development]]
[[Category:Development (English)]]
+
[[it:VCS PKGBUILD Guidelines]]
[[Category:Package development (English)]]
+
[[zh-CN:VCS PKGBUILD Guidelines]]
[[Category:HOWTOs (English)]]
+
[[zh-TW:VCS PKGBUILD Guidelines]]
[[Category:Guidelines (English)]]
+
{{Package Guidelines}}
  
:''This is actually very easy and doesn't require any special knowledge. However, the more you know about cvs and svn the easier it is.  Many people introduce custom variables into the PKGBUILD that can overcomplicate things.  These are not ''really'' necessary but do help to clarify the syntax of the cvs/svn/git commands, which can appear quite complex.''
+
[[Wikipedia:Revision_control|Version control systems]] can be used for retrieval of source code for both usual statically versioned packages and latest (trunk) version of packages. This article covers both cases.
  
{{i18n_links_start}}
+
== Prototypes ==
{{i18n_entry|English|Arch CVS %26 SVN PKGBUILD guidelines}}
+
The [[ABS]] package provides prototypes for [[cvs]], [[svn]], [[git]], [[mercurial]], and [[Wikipedia:darcs|darcs]] [[PKGBUILD]]s. When {{Pkg|abs}} is installed, you can find them in {{ic|/usr/share/pacman}}. Latest versions can be found in the [https://projects.archlinux.org/abs.git/tree/prototypes prototypes directory in the ABS Git repository].
{{i18n_entry|繁體中文|Arch CVS %26 SVN PKGBUILD 編寫指南}}
+
{{i18n_entry|简体中文|Arch CVS %26 SVN %26 GIT PKGBUILD 编写指南}}
+
{{i18n_links_end}}
+
  
 +
== Guidelines ==
 +
* Properly suffix {{Ic|pkgname}} with {{Ic|-cvs}}, {{Ic|-svn}}, {{Ic|-hg}}, {{Ic|-darcs}}, {{Ic|-bzr}}, {{Ic|-git}} etc. If the package tracks a moving development trunk it should be given a suffix. If the package fetches a release from a VCS tag then it should not be given a suffix. Use this rule of thumb: if the output of the package depends on the time at which it was compiled, append a suffix; otherwise do not.
  
==A few tips==
+
* A VCS package may be updated as and when needed to adopt changes to the build system, including ammendments to dependencies, URL, sources, etc. If the revision number remains the same after such an update, but produces a resulting binary which is different, increasing the {{Ic|pkgrel}} is mandatory. If both the revision number and the resulting binary remain the same, {{Ic|pkgrel}} should be kept intact. There is no need to update the VCS package just to accommodate a revision bump, but one may choose to do so.
  
* Suffix <code>pkgname</code> with <code>-cvs</code> or <code>-svn</code> or <code>-git</code> where applicable - this prevents confusion with non-development versions e.g. fluxbox-svn or fvwm-cvs vs fluxbox and fvwm.
+
* When [[makepkg]] is run, by default it will check for newer revisions and then update the {{Ic|pkgver}} in the PKGBUILD. Look at {{Ic|--holdver}} in [http://www.archlinux.org/pacman/makepkg.8.html man makepkg] if you want otherwise{{Ic|--holdver}} only works for cvs and svn, which allow checkout of older revisions.
* When makepkg is run it will check for newer revisions and then bump pkgver to the latest. If this is not what you want see the --holdver in [http://www.archlinux.org/pacman/makepkg.8.html man makepkg]
+
* You must also be careful about pacman conflictsFor example fluxbox-svn will conflict with fluxbox.  In this case you need to use the <tt>conflicts=</tt> field
+
conflicts=('fluxbox')
+
: You should also use the <tt>provides=</tt> field so that pkgs that require fluxbox to be installed recognize your fluxbox-svn pkg as fluxbox
+
provides=('fluxbox')
+
: You should AVOID using <tt>replaces=</tt> it generally causes unnecessary problems
+
*When using/defining the cvsroot use anonymous<b>:</b>@ rather than anonymous@ to avoid having to press enter to give blank password ''OR'' anonymous<b>:password</b>@ - if a password is required.
+
* cvs and svn PKGBUILDs may not require a source or md5sum array but these fields '''must''' be included in the PKGBUILD if you wish to submit it to the AUR, otherwise the pkg will be rejected.  They may be left blank though.
+
<pre>source=()
+
md5sums=()</pre>
+
* Though it is often unneccesary to use the pkgrel field when building CVS/SVN/GIT pkgs (any changes to the pkg will often be on another day and so are usually accounted for by a change in pkgver [assuming pkgver is used to hold a date format], makepkg will require it.
+
* don't forget to include cvs or subversion in <code>makedepends=</code> as necessary
+
* to preserve the integrity of the checked out code it is usually possible to build in a separate build dir e.g. having checked out source code to src/$_cvsmod from $startdir you can use:
+
<pre>  mkdir src/$_cvsmod-build
+
  
  cd src/$_cvsmod-build
+
* Check for package conflicts. For example ''fluxbox-svn'' will conflict with ''fluxbox''. In this case, you need to use {{Ic|1=conflicts=('fluxbox')}}.
  ../$_cvsmod/configure</pre>
+
''OR'' if that fails you can try:
+
<pre> cp -r src/$_cvsmod src/$_cvsmod-build
+
  cd src/$_cvsmod-build</pre>
+
  
* With the introduction of the AUR it is most important to avoid using backtick execution to create pkg variables
+
* Use the {{Ic|provides}} field so that packages that require the non-VCS package can be installed ({{Ic|1=provides=('fluxbox')}}).
** For cvs pkgs you should avoid <code>pkgver=`date +%y%m%d`</code> - this also interferes with the functionality of the AUR.  Instead it is still possible to use a date format for the $pkgver variable and to use the cvs -D option to check out code from that date (see below)
+
** For svn you can use the revision number.  An easy way to find the revision number is to use the following command:
+
svn log $_svntrunk --limit 1 | sed -e '/^r/!d' -e 's/^r\([0-9]\+\) .*/\1/;q'
+
That command grabs the most recent log entry from the svn repo and finds the revision number, which is prefixed with an r.  This is from the fluxbox svn log, the revision number is in the top left, r4084
+
<pre>
+
------------------------------------------------------------------------
+
r4084 | mathias | 2005-07-20 19:29:01 +0100 (Wed, 20 Jul 2005) | 16 lines
+
  
Changed some *Focus options, just to make some things a bit more clear.
+
* You should AVOID using {{Ic|1=replaces=...}} as it generally causes unnecessary problems.
the "Sloppy" was always a bit .. imprecise.
+
</pre>
+
  
==Example CVS PKGBUILD==
+
* When using/defining the cvsroot, use {{Ic|anonymous:@}} rather than {{Ic|anonymous@}} to avoid a password prompt and having to enter a blank password ''OR'' use {{Ic|anonymous:password@}} if a password is required.
  
Here is a PKGBUILD for bmp-cvs that utilizes some of the tips above:
+
* Don't forget to include the appropriate VCS tool (cvs, subversion, git, ...) in {{Ic|1=makedepends=...}}.
  
<pre># Contributor: Lukas Sabota <punkrockguy318@comcast.net>
+
* 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 {{ic|src/$_cvsmod}} from {{ic|$startdir}} you can use:
# Contributor: dibblethewrecker dibblethewrecker.at.jiwe.dot.org
+
  
pkgname=bmp-cvs
+
mkdir src/$_cvsmod-build
pkgver=20050728
+
pkgrel=1
+
cd src/$_cvsmod-build
pkgdesc="A multimedia player that uses the WinAmp 2.x UI, GTK2, and is based on XMMS"
+
../$_cvsmod/configure
url="http://beepmp.sourceforge.net/"
+
arch=('i686' 'x86_64')
+
license=('GPL')
+
depends=('gtk2' 'libvorbis' 'alsa-lib' 'audiofile' 'libglade' 'id3lib' 'x-server')
+
provides=('bmp')
+
conflicts=('bmp')
+
makedepends=('cvs')
+
install=(${pkgname}.install)
+
  
_cvsroot=":pserver:anonymous:@beepmp.cvs.sourceforge.net:/cvsroot/beepmp"
+
or:
_cvsmod="bmp"
+
  
build() {
+
cp -r src/$_cvsmod src/$_cvsmod-build
  cd ${srcdir}
+
cd src/$_cvsmod-build
  
  msg "Connecting to $_cvsmod.sourceforge.net CVS server...."
+
* With the introduction of the [[AUR]], it is most important to avoid using backtick execution to create package variables. makepkg will automatically bump the {{Ic|pkgver}} anyway when building the package (unless {{Ic|--holdver}} is used).
  if [ -d $_cvsmod/CVS ]; then
+
    cd $_cvsmod
+
    cvs -z3 update -d
+
  else
+
    cvs -z3 -d $_cvsroot co -D $pkgver -f $_cvsmod
+
    cd $_cvsmod
+
  fi
+
  ./autogen.sh
+
  
  msg "CVS checkout done or server timeout"
+
== Tips ==
  msg "Starting make..."
+
* You should make sure that there are no VCS directories and files left over in your package. If there are, you may want to remove them, by adding a command similar to this one at the end of the the package() script:
  
  cp -r ../$_cvsmod ../$_cvsmod-build
+
rm -rf $(find "$pkgdir" -type d -name ".svn")
  cd ../$_cvsmod-build
+
  
  ./configure --prefix=/usr
+
* When using Git, one can speed up the cloning operation using the {{Ic|1=--depth=1}} parameter. This creates a shallow clone, and has only the last change history - since histories are unimportant for builds most of the time.
  make || return 1
+
  make DESTDIR=${pkgdir} install || return 1
+
  
  install -d ${pkgdir}/usr/share/xmms/Skins
+
git clone git://hostname.dom/project.git --depth=1
  mv ${pkgdir}/usr/share/bmp/Skins/* ${pkgdir}/usr/share/xmms/Skins
+
  rmdir ${pkgdir}/usr/share/bmp/Skins
+
  
  rm -r ${srcdir}/$_cvsmod-build
+
* It's possible to create the package also from a branch other than the master. To do so add {{Ic|1=--branch branch_name}} after the first {{Ic|1=git clone}}, in this way:
}
+
# vim:syntax=sh
+
</pre>
+
  
==Example SVN PKGBUILD==
+
git clone "$_gitroot" "$_gitname" --branch branch_name
 +
Remember to save package with a different name, for example {{Ic|1= pkgname-branchname-git}}, in order to avoid confusion with the package from the branch master.
  
If you use the <tt>source</tt> command on the PKGBUILD first it will store the _svntrunk and _svnmod variables. So if you run :
+
* Copy paste script when building from repo
source PKGBUILD
+
If you are lazy here is a sample script when making git-based PKGBUILDs.
svn info $_svntrunk
+
you can get the revision number(Or,Last Changed Rev) which can be used in pkgver
+
  
<pre>
+
  cd "$srcdir"
# Contributor:  Lukas Sabota <punkrockguy318@comcast.net>
+
  msg "Connecting to GIT server..."
# Contributor: dibblethewrecker dibblethewrecker.at.jiwe.dot.org
+
   if [ -d $_gitname ] ; then
 
+
     cd $_gitname && git pull origin
pkgname=fluxbox-svn
+
    msg "The local files are updated."
pkgver=4084
+
pkgrel=1
+
pkgdesc="The bleeding edge version of a lightweight yet \
+
        customizable windowmanager for X"
+
url="http://www.fluxbox.org/"
+
arch=('i686' 'x86_64')
+
license=('GPL')
+
depends=('bash' 'x-server')
+
makedepends=('subversion')
+
conflicts=('blackbox' 'fluxbox' 'fluxbox-devel' 'fluxbox-cvs')
+
provides=('fluxbox')
+
 
+
source=()
+
md5sums=()
+
 
+
_svntrunk=svn://svn.berlios.de/fluxbox/trunk
+
_svnmod=fluxbox
+
 
+
build() {
+
  cd ${srcdir}
+
 
+
   if [ -d $_svnmod/.svn ]; then
+
     (cd $_svnmod && svn up -r $pkgver)
+
 
   else
 
   else
     svn co $_svntrunk --config-dir ./ -r $pkgver $_svnmod
+
     git clone --depth=1 $_gitroot $_gitname
 
   fi
 
   fi
 
  msg "SVN checkout done or server timeout"
 
  msg "Starting make..."
 
 
  cp -r $_svnmod $_svnmod-build
 
  cd $_svnmod-build
 
 
  ./autogen.sh
 
 
  # fix for crap fb issue
 
  mkdir data
 
  cp ../$_svnmod/data/keys data/
 
 
  ./configure --prefix=/usr --enable-xinerama --enable-imlib2 --enable-debug
 
  make || return 1
 
  make DESTDIR=${pkgdir} install || return 1
 
 
  rm -rf ${srcdir}/$_svnmod-build
 
}
 
# vim:syntax=sh</pre>
 
 
==Example GIT PKGBUILD==
 
 
<pre>
 
# Contributor: Your Name <your@mail.org>
 
 
pkgname=compiz-git
 
pkgver=20080523
 
pkgrel=1
 
pkgdesc="Composite and window manager for Xgl"
 
url="http://en.opensuse.org/Compiz"
 
arch=('i686' 'x86_64')
 
license=('GPL')
 
depends=('xgl-cvs' 'mesa-xgl-cvs' 'cairo-devel' 'libxevie' \
 
        'startup-notification' 'libpng'  'libxdamage' \
 
        'libxrandr' 'libwnck-compiz' 'gnome-desktop' 'control-center' \
 
        'libsvg-cairo' 'libxcomposite')
 
makedepends=('git')
 
conflicts=()
 
replaces=()
 
backup=()
 
install=('compiz.install')
 
source=(compiz-intel-copy-pixel-issue-workaround-1.diff)
 
md5sums=('10a157b86d528bca2be6731c5eaff7b3')
 
 
_gitroot="git://anongit.freedesktop.org/git/xorg/app/compiz"
 
_gitname="compiz"
 
 
build() {
 
export CFLAGS="$CFLAGS -I/opt/mesa-xgl-cvs/include"
 
  cd ${srcdir}
 
  msg "Connecting to git.freedesktop.org GIT server...."
 
 
  if [ -d ${srcdir}/$_gitname ] ; then
 
  cd $_gitname && git pull origin
 
  msg "The local files are updated."
 
  else
 
  git clone --depth 1 $_gitroot $_gitname
 
  fi
 
 
 
   msg "GIT checkout done or server timeout"
 
   msg "GIT checkout done or server timeout"
  msg "Starting make..."
 
 
  git clone $_gitname $_gitname-build
 
  cd ${srcdir}/$_gitname-build
 
  patch -Np0 -i ${srcdir}/compiz-intel-copy-pixel-issue-workaround-1.diff
 
 
  ACLOCAL="aclocal -I /opt/gnome/share/aclocal" ./autogen.sh --host=${CHOST} \
 
    --prefix=/usr \
 
    --infodir=/usr/share/info \
 
    --mandir=/usr/share/man \
 
    --sysconfdir=/opt/gnome/etc \
 
    --enable-gnome \
 
    --enable-libsvg-cairo \
 
    --enable-gconf-dump \
 
    --disable-kde || return 1
 
  make || return 1
 
  make DESTDIR=${pkgdir} install || return 1
 
 
  find ${pkgdir} -type f -name '*.la' -exec rm {} \;
 
}
 
</pre>
 
As you see, I use "-git" suffix in the pkgname, and two variables, _gitroot and _gitname for identify the repositories and the name of the package.
 
I need to introduce an if condition:
 
<pre>
 
if [ -d ${srcdir}/$_gitname ] ; then
 
cd $_gitname && git pull origin
 
msg "The local files are updated."
 
else
 
git clone --depth 1 $_gitroot $_gitname
 
fi
 
</pre>
 
because we have two commands, one for updating source and one for getting it. I copy the source code in a "-build" directory ( the same thing that we do with -cvs and -svn program ).
 
 
==Example darcs PKGBUILD==
 
<pre>
 
# Contributor: Your Name <your@mail.org>
 
 
pkgname=psi-darcs
 
pkgver=20070404
 
pkgrel=2
 
pkgdesc="Psi - Jabber client (with SSL support) darcs version"
 
url="http://psi-im.org/"
 
arch=('i686' 'x86_64')
 
license=('')
 
depends=('qt4>=4.2' 'openssl' 'libxss' 'cyrus-sasl' 'aspell')
 
makedepends=('darcs' 'qt4>=4.2')
 
conflicts=('psi')
 
provides=('psi')
 
source=()
 
md5sums=()
 
 
_darcsmod="psi"
 
_darcstrunk="http://dev.psi-im.org/darcs"
 
 
build() {
 
  cd ${srcdir}
 
 
  # Erasing previous build
 
  msg "Checking for previous build"
 
  # get the sources
 
  if [[ -d $_darcsmod/_darcs ]]
 
  then
 
    msg "Retrieving missing patches"
 
    cd $_darcsmod
 
    darcs pull -a $_darcstrunk/$_darcsmod
 
  else
 
    msg "Retrieving complete sources"
 
    darcs get --partial --set-scripts-executable $_darcstrunk/$_darcsmod
 
    cd $_darcsmod
 
  fi
 
 
  . /etc/profile.d/qt4.sh
 
  export PATH=$QTDIR/bin:$PATH
 
 
  # Building
 
  msg "Starting build"
 
  ./configure --prefix=/usr --disable-xmms
 
  make || return 1
 
  make INSTALL_ROOT=${pkgdir} install || return 1
 
}
 
</pre>
 
 
==rc-script PROTO==
 
<pre>
 
#!/bin/bash
 
 
daemon_name=DAEMON_NAME
 
 
. /etc/rc.d/functions
 
 
. /etc/conf.d/$daemon_name.conf
 
 
. /etc/rc.conf
 
 
get_pid() {
 
      pidof $daemon_name
 
}
 
 
case "$1" in
 
start)
 
  stat_busy "Starting $daemon_name daemon"
 
  
  PID=`get_pid`
+
* Temporary build directories: When using Git, and where you need to create a separate build directory (e.g., for building/compiling), you should avoid copying over the {{Ic|1=.git}} directory located in the parent folder because it contains history information that Git uses internally. With repos with thousands of commits, this .git directory will contain upwards of hundreds of MiB of useless commit history that has *nothing* to do with the current working tree. The only time you'd need to copy over the .git directory itself is when you need to build from a specific, older commit (which is generally never the case as the point of a VCS PKGBUILD is to pull from the latest bleeding edge commit). Thus, instead of
  if [ -z "$PID" ]; then
+
    [ -f /var/run/$daemon_name.pid ] && rm -f /var/run/$daemon_name.pid
+
    # RUN
+
    $daemon_name
+
    #
+
    if [ $? -gt 0 ]; then
+
      stat_fail
+
      exit 1
+
    else
+
      echo `get_pid` > /var/run/$daemon_name.pid
+
      add_daemon $daemon_name
+
      stat_done
+
    fi
+
  else
+
    stat_fail
+
    exit 1
+
  fi
+
  ;;
+
  
  stop)
+
  rm -rf "$srcdir/$_gitname-build"
  stat_busy "Stopping $daemon_name daemon"
+
cp -R "$srcdir/$_gitname" "$srcdir/$_gitname-build" # copy everything, including the useless .git folder
  PID=`get_pid`
+
cd "$srcdir/$_gitname-build"
  # KILL
+
make # build/compile from source
  [ ! -z "$PID" ] && kill $PID &> /dev/null
+
  #
+
  if [ $? -gt 0 ]; then
+
    stat_fail
+
    exit 1
+
  else
+
    rm -f /var/run/$daemon_name.pid &> /dev/null
+
    rm_daemon $daemon_name
+
    stat_done
+
  fi
+
  ;;
+
  
restart)
+
you should do
  $0 stop
+
  sleep 3
+
  $0 start
+
  ;;
+
*)
+
  echo "usage: $0 {start|stop|restart}"
+
esac
+
exit 0
+
</pre>
+
  
== Useful Links ==
+
rm -rf "$srcdir/$_gitname-build"
 +
cd "$srcdir/$_gitname" && ls -A | grep -v .git | xargs -d '\n' cp -r -t ../$_gitname-build # do not copy over the .git folder
 +
cd "$srcdir/$_gitname-build"
 +
make # build/compile from source
  
* [[The Arch package making HOW-TO - with guidelines]]
+
to cut down on build time and disk usage.
* [http://aur.archlinux.org AUR]
+
* [[ABS_-_The_Arch_Build_System | ABS - The Arch Build System]]
+
* [[ABS PKGBUILD Explained]]
+
* [[Makepkg]]
+
* [[PKGBUILD Tricks]]
+

Revision as of 09:28, 14 June 2012

Template:Package Guidelines

Version control systems can be used for retrieval of source code for both usual statically versioned packages and latest (trunk) version of packages. This article covers both cases.

Prototypes

The ABS package provides prototypes for cvs, svn, git, mercurial, and darcs PKGBUILDs. When abs is installed, you can find them in /usr/share/pacman. Latest versions can be found in the prototypes directory in the ABS Git repository.

Guidelines

  • Properly suffix pkgname with -cvs, -svn, -hg, -darcs, -bzr, -git etc. If the package tracks a moving development trunk it should be given a suffix. If the package fetches a release from a VCS tag then it should not be given a suffix. Use this rule of thumb: if the output of the package depends on the time at which it was compiled, append a suffix; otherwise do not.
  • A VCS package may be updated as and when needed to adopt changes to the build system, including ammendments to dependencies, URL, sources, etc. If the revision number remains the same after such an update, but produces a resulting binary which is different, increasing the pkgrel is mandatory. If both the revision number and the resulting binary remain the same, pkgrel should be kept intact. There is no need to update the VCS package just to accommodate a revision bump, but one may choose to do so.
  • When makepkg is run, by default it will check for newer revisions and then update the pkgver in the PKGBUILD. Look at --holdver in man makepkg if you want otherwise. --holdver only works for cvs and svn, which allow checkout of older revisions.
  • Check for package conflicts. For example fluxbox-svn will conflict with fluxbox. In this case, you need to use conflicts=('fluxbox').
  • Use the provides field so that packages that require the non-VCS package can be installed (provides=('fluxbox')).
  • You should AVOID using replaces=... as it generally causes unnecessary problems.
  • When using/defining the cvsroot, use anonymous:@ rather than anonymous@ to avoid a password prompt and having to enter a blank password OR use anonymous:password@ if a password is required.
  • Don't forget to include the appropriate VCS tool (cvs, subversion, git, ...) in makedepends=....
  • 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 src/$_cvsmod from $startdir 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 pkgver anyway when building the package (unless --holdver is used).

Tips

  • You should make sure that there are no VCS directories and files left over in your package. If there are, you may want to remove them, by adding a command similar to this one at the end of the the package() script:
rm -rf $(find "$pkgdir" -type d -name ".svn")
  • When using Git, one can speed up the cloning operation using the --depth=1 parameter. This creates a shallow clone, and has only the last change history - since histories are unimportant for builds most of the time.
git clone git://hostname.dom/project.git --depth=1
  • It's possible to create the package also from a branch other than the master. To do so add --branch branch_name after the first git clone, in this way:
git clone "$_gitroot" "$_gitname" --branch branch_name

Remember to save package with a different name, for example pkgname-branchname-git, in order to avoid confusion with the package from the branch master.

  • Copy paste script when building from repo

If you are lazy here is a sample script when making git-based PKGBUILDs.

 cd "$srcdir"
 msg "Connecting to GIT server..."
 if [ -d $_gitname ] ; then
   cd $_gitname && git pull origin
   msg "The local files are updated."
 else
   git clone --depth=1 $_gitroot $_gitname
 fi
 msg "GIT checkout done or server timeout"
  • Temporary build directories: When using Git, and where you need to create a separate build directory (e.g., for building/compiling), you should avoid copying over the .git directory located in the parent folder because it contains history information that Git uses internally. With repos with thousands of commits, this .git directory will contain upwards of hundreds of MiB of useless commit history that has *nothing* to do with the current working tree. The only time you'd need to copy over the .git directory itself is when you need to build from a specific, older commit (which is generally never the case as the point of a VCS PKGBUILD is to pull from the latest bleeding edge commit). Thus, instead of
rm -rf "$srcdir/$_gitname-build"
cp -R "$srcdir/$_gitname" "$srcdir/$_gitname-build" # copy everything, including the useless .git folder
cd "$srcdir/$_gitname-build"
make # build/compile from source

you should do

rm -rf "$srcdir/$_gitname-build"
cd "$srcdir/$_gitname" && ls -A | grep -v .git | xargs -d '\n' cp -r -t ../$_gitname-build # do not copy over the .git folder
cd "$srcdir/$_gitname-build"
make # build/compile from source

to cut down on build time and disk usage.