git-annex/Git/Version.hs

{- git versions
 -
 - Copyright 2011, 2013 Joey Hess <id@joeyh.name>
 -
 - Licensed under the GNU AGPL version 3 or higher.
 -}

{-# OPTIONS_GHC -fno-warn-tabs #-}

module Git.Version (
	installed,
	older,
	normalize,
	GitVersion,
) where

import Utility.Process
import Utility.DottedVersion

type GitVersion = DottedVersion

installed :: IO GitVersion
installed = normalize . extract <$> readProcess "git" ["--version"]
  where
	extract s = case lines s of
		[] -> ""
		(l:_) -> unwords $ drop 2 $ words l

older :: String -> IO Bool
older n = do
	v <- installed
	return $ v < normalize n
better git version checking 2013-08-02 22:31:01 +00:00			`{- git versions`
Can now be built with older git versions (before 1.7.7); the resulting binary should only be used with old git. Remove git old version check from configure, and use the git version it was built against in the git check-attr code. 2011-12-22 18:59:25 +00:00			`-`
update my email address and homepage url 2015-01-21 16:50:09 +00:00			`- Copyright 2011, 2013 Joey Hess <id@joeyh.name>`
Can now be built with older git versions (before 1.7.7); the resulting binary should only be used with old git. Remove git old version check from configure, and use the git version it was built against in the git check-attr code. 2011-12-22 18:59:25 +00:00			`-`
update licenses from GPL to AGPL This does not change the overall license of the git-annex program, which was already AGPL due to a number of sources files being AGPL already. Legally speaking, I'm adding a new license under which these files are now available; I already released their current contents under the GPL license. Now they're dual licensed GPL and AGPL. However, I intend for all my future changes to these files to only be released under the AGPL license, and I won't be tracking the dual licensing status, so I'm simply changing the license statement to say it's AGPL. (In some cases, others wrote parts of the code of a file and released it under the GPL; but in all cases I have contributed a significant portion of the code in each file and it's that code that is getting the AGPL license; the GPL license of other contributors allows combining with AGPL code.) 2019-03-13 19:48:14 +00:00			`- Licensed under the GNU AGPL version 3 or higher.`
Can now be built with older git versions (before 1.7.7); the resulting binary should only be used with old git. Remove git old version check from configure, and use the git version it was built against in the git check-attr code. 2011-12-22 18:59:25 +00:00			`-}`

more {-# OPTIONS_GHC -fno-warn-tabs #-} ... Forcing people who have what is merely a difference of opinion to you to do this is a bit of an asshole move. Just saying. 2015-05-10 20:38:49 +00:00			`{-# OPTIONS_GHC -fno-warn-tabs #-}`

Use wget -q --show-progress for less verbose wget output, when built with wget 1.16. 2014-12-16 18:04:40 +00:00			`module Git.Version (`
			`installed,`
Check git version at runtime, rather than assuming it will be the same as the git version used at build time when running git-checkattr and git-branch remove. It's ok to probe every time for git-branch remove because that's run quite rarely. For git-checkattr, it's run only once, when starting the --batch mode, and so again the overhead is pretty minimal. This leaves 2 places where the build version is still used. git merge might be interactive or fail if one skews, and --no-gpg-sign might not be pased, or might be passed to a git that doesn't understand it if the other skews. It seems a little expensive to check the git version each time these are used. This doesn't seem likely to cause many problems, at least compared with check-attr hanging on skew. 2015-01-05 19:54:52 +00:00			`older,`
Use wget -q --show-progress for less verbose wget output, when built with wget 1.16. 2014-12-16 18:04:40 +00:00			`normalize,`
			`GitVersion,`
			`) where`
Can now be built with older git versions (before 1.7.7); the resulting binary should only be used with old git. Remove git old version check from configure, and use the git version it was built against in the git check-attr code. 2011-12-22 18:59:25 +00:00
more RawFilePath conversion At 318/645 after 4k lines of changes This commit was sponsored by Jake Vosloo on Patreon. 2020-10-29 16:02:46 +00:00			`import Utility.Process`
Use wget -q --show-progress for less verbose wget output, when built with wget 1.16. 2014-12-16 18:04:40 +00:00			`import Utility.DottedVersion`
Can now be built with older git versions (before 1.7.7); the resulting binary should only be used with old git. Remove git old version check from configure, and use the git version it was built against in the git check-attr code. 2011-12-22 18:59:25 +00:00
Use wget -q --show-progress for less verbose wget output, when built with wget 1.16. 2014-12-16 18:04:40 +00:00			`type GitVersion = DottedVersion`
better git version checking 2013-08-02 22:31:01 +00:00
			`installed :: IO GitVersion`
			`installed = normalize . extract <$> readProcess "git" ["--version"]`
			`where`
fix some mixed space+tab indentation This fixes all instances of " \t" in the code base. Most common case seems to be after a "where" line; probably vim copied the two space layout of that line. Done as a background task while listening to episode 2 of the Type Theory podcast. 2014-10-09 18:53:13 +00:00			`extract s = case lines s of`
better git version checking 2013-08-02 22:31:01 +00:00			`[] -> ""`
			`(l:_) -> unwords $ drop 2 $ words l`
Check git version at runtime, rather than assuming it will be the same as the git version used at build time when running git-checkattr and git-branch remove. It's ok to probe every time for git-branch remove because that's run quite rarely. For git-checkattr, it's run only once, when starting the --batch mode, and so again the overhead is pretty minimal. This leaves 2 places where the build version is still used. git merge might be interactive or fail if one skews, and --no-gpg-sign might not be pased, or might be passed to a git that doesn't understand it if the other skews. It seems a little expensive to check the git version each time these are used. This doesn't seem likely to cause many problems, at least compared with check-attr hanging on skew. 2015-01-05 19:54:52 +00:00
			`older :: String -> IO Bool`
			`older n = do`
			`v <- installed`
work around git "defense in depth" breakage with git clone checking for hooks This git bug also broke git-lfs, and I am confident it will be reverted in the next release. For now, cloning from an annex:: url wastes some bandwidth on the next pull by not caching bundles locally. If git doesn't fix this in the next version, I'd be tempted to rethink whether bundle objects need to be cached locally. It would be possible to instead remember which bundles have been seen and their heads, and respond to the list command with the heads, and avoid unbundling them agian in fetch. This might even be a useful performance improvement in the latter case. It would be quite a complication to a currently simple implementation though. 2024-05-24 19:49:53 +00:00			`return $ v < normalize n`