40ecf58d4bThis 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.)
21 lines
576 B
Haskell
21 lines
576 B
Haskell
{- git build version
|
|
-
|
|
- Copyright 2011 Joey Hess <id@joeyh.name>
|
|
-
|
|
- Licensed under the GNU AGPL version 3 or higher.
|
|
-}
|
|
|
|
module Git.BuildVersion where
|
|
|
|
import Git.Version
|
|
import qualified BuildInfo
|
|
|
|
{- Using the version it was configured for avoids running git to check its
|
|
- version, at the cost that upgrading git won't be noticed.
|
|
- This is only acceptable because it's rare that git's version influences
|
|
- code's behavior. -}
|
|
buildVersion :: GitVersion
|
|
buildVersion = normalize BuildInfo.gitversion
|
|
|
|
older :: String -> Bool
|
|
older n = buildVersion < normalize n
|