Difference between revisions of "Talk:VCS package guidelines"
m (moved Talk:Arch CVS & SVN PKGBUILD guidelines to Talk:VCS PKGBUILD guidelines: This page is not specific to cvs and svn...)
Revision as of 11:21, 4 October 2009
Q: Any reason for using 'svn co' instead of 'svn export'? export is way faster for these situations and it doesn't create all the .svn files.
Just wondering if the versionpkg part will be removed - I hear that makepkg now has versionpkgs functionality... --ak5 16:55, 8 June 2008 (EDT)
-- done (wide-eye)
The title for this article indicate guidelines for CVS and SVN, but git and darcs are also included. Perhaps the title should be changed to reflect this, or git and darcs guidelines should be separated off into their own articles. --mentallaxative 01:48, 18 October 2008 (EDT)
- I agree. --Matthewbauer 17:16, 21 July 2009 (EDT)
What's the reason for using 'cp -r $_svnmod $_svnmod-build' instead of using 'svn export $_svnmod $_svnmod-build'?--BertiBoeller 19:21, 15 March 2009 (EDT)
Does the AUR still reject PKGBUILDs without a source=() and md5sum=() field? I don't think so - I have many PKGBUILDs up without them. Alex anthony 20:29, 12 August 2009 (EDT)