Difference between revisions of "Talk:VCS package guidelines"

From ArchWiki
Jump to: navigation, search
(Clean-up)
(Suggestions)
Line 6: Line 6:
 
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)?
 
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)?
 
--[[User:Mitch feaster|Mitch feaster]] 14:34, 15 November 2011 (EST)
 
--[[User:Mitch feaster|Mitch feaster]] 14:34, 15 November 2011 (EST)
 +
 +
 +
 +
Can we stop suggesting git describe --always when you want to get the hash of the last commit? That only valid if there's no tags; if the author later creates a tag, everything gets screwed up. git rev-parse --short HEAD is a much better solution. [[User:Scimmia|Scimmia]] ([[User talk:Scimmia|talk]]) 07:15, 9 April 2013 (UTC)

Revision as of 07:15, 9 April 2013

Comments

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)

Suggestions

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)


Can we stop suggesting git describe --always when you want to get the hash of the last commit? That only valid if there's no tags; if the author later creates a tag, everything gets screwed up. git rev-parse --short HEAD is a much better solution. Scimmia (talk) 07:15, 9 April 2013 (UTC)