Difference between revisions of "Talk:VCS package guidelines"

From ArchWiki
Jump to: navigation, search
Line 13: Line 13:
  ''→‎Subversion:  $SRCDEST not necessary''
  ''→‎Subversion:  $SRCDEST not necessary''
Wrong, see the [[VCS_PKGBUILD_Guidelines#Subversion|note]] you left behind. The VCS directory ({{ic|.svn}}) is not copied for SVN, which means it doesn't work:
Wrong, see the [[VCS_PKGBUILD_Guidelines#Subversion|note]] you left behind. {{ic|svn export}} doesn't copy {{ic|.svn}}, which means getting the version won't work anymore:
{{hc|[$srcdir]$ svnversion|
{{hc|[$srcdir]$ svnversion|
Unversioned directory
Unversioned directory

Revision as of 16:46, 10 April 2013


I don't use cvs. How can you describe the pkgver for cvs (for pacman 4.1)? --Dracorp (talk) 09:31, 6 April 2013 (UTC)


Could we consider a guideline to use firewall-friendly protocols when possible (e.g. https://github.com/matplotlib/matplotlib.git instead of git://github.com/matplotlib/matplotlib.git)? --Mitch feaster 14:34, 15 November 2011 (EST)

Since Thestinger decided to protect the entire page (for whatever reason):

1) Thestinger's change (7:03, 10 April 2013 (UTC)):

→‎Subversion:  $SRCDEST not necessary

Wrong, see the note you left behind. svn export doesn't copy .svn, which means getting the version won't work anymore:

[$srcdir]$ svnversion
Unversioned directory

2) Danielwallace's change (04:32, 10 April 2013 (UTC)):

pkgver() {
   cd local_repo
−  git rev-list --count HEAD
+  echo $(git rev-list --count master).$(git rev-parse --short master)
- [...]

That's good but you left the title and the sample output intact. Also, the first example still uses git describe --always.

--Det (talk) 16:41, 10 April 2013 (UTC)

Thanks, reverted. -- thestinger (talk) 16:45, 10 April 2013 (UTC)