2011-08-17 18:14:43 +00:00
|
|
|
{- git-annex repository initialization
|
|
|
|
-
|
2011-08-17 22:42:49 +00:00
|
|
|
- Copyright 2011 Joey Hess <joey@kitenet.net>
|
2011-08-17 18:14:43 +00:00
|
|
|
-
|
|
|
|
- Licensed under the GNU GPL version 3 or higher.
|
|
|
|
-}
|
|
|
|
|
2013-05-11 20:03:00 +00:00
|
|
|
{-# LANGUAGE CPP #-}
|
|
|
|
|
2014-01-26 20:36:31 +00:00
|
|
|
module Annex.Init (
|
2011-08-17 22:38:26 +00:00
|
|
|
ensureInitialized,
|
2012-07-31 20:19:24 +00:00
|
|
|
isInitialized,
|
2011-08-17 18:36:20 +00:00
|
|
|
initialize,
|
2014-04-16 00:13:35 +00:00
|
|
|
initialize',
|
2013-02-15 18:17:31 +00:00
|
|
|
uninitialize,
|
2013-11-05 19:29:56 +00:00
|
|
|
probeCrippledFileSystem,
|
2011-08-17 18:36:20 +00:00
|
|
|
) where
|
2011-08-17 18:14:43 +00:00
|
|
|
|
2011-10-05 20:02:51 +00:00
|
|
|
import Common.Annex
|
2013-05-14 00:48:44 +00:00
|
|
|
import qualified Annex
|
2011-08-17 18:14:43 +00:00
|
|
|
import qualified Git
|
2013-02-15 22:16:50 +00:00
|
|
|
import qualified Git.LsFiles
|
2013-04-04 17:14:55 +00:00
|
|
|
import qualified Git.Config
|
2014-09-05 17:44:09 +00:00
|
|
|
import qualified Git.Objects
|
2011-10-04 04:40:47 +00:00
|
|
|
import qualified Annex.Branch
|
2011-11-02 18:18:21 +00:00
|
|
|
import Logs.UUID
|
2014-09-05 17:44:09 +00:00
|
|
|
import Logs.Trust.Basic
|
|
|
|
import Types.TrustLevel
|
2011-10-04 04:40:47 +00:00
|
|
|
import Annex.Version
|
2011-10-15 21:47:03 +00:00
|
|
|
import Annex.UUID
|
2013-02-14 18:10:36 +00:00
|
|
|
import Config
|
2013-02-15 22:16:50 +00:00
|
|
|
import Annex.Direct
|
2013-02-20 17:55:53 +00:00
|
|
|
import Annex.Content.Direct
|
2013-07-05 16:24:28 +00:00
|
|
|
import Annex.Environment
|
2013-02-15 22:16:50 +00:00
|
|
|
import Backend
|
2014-12-29 21:25:59 +00:00
|
|
|
import Annex.Hook
|
|
|
|
import Upgrade
|
2013-08-04 17:07:55 +00:00
|
|
|
#ifndef mingw32_HOST_OS
|
|
|
|
import Utility.UserInfo
|
|
|
|
import Utility.FileMode
|
2014-12-29 21:25:59 +00:00
|
|
|
import Annex.Perms
|
2013-08-04 17:07:55 +00:00
|
|
|
#endif
|
2012-08-03 14:45:18 +00:00
|
|
|
|
|
|
|
genDescription :: Maybe String -> Annex String
|
|
|
|
genDescription (Just d) = return d
|
|
|
|
genDescription Nothing = do
|
2013-05-11 20:03:00 +00:00
|
|
|
reldir <- liftIO . relHome =<< fromRepo Git.repoPath
|
2013-04-03 07:52:41 +00:00
|
|
|
hostname <- fromMaybe "" <$> liftIO getHostname
|
2013-08-04 17:07:55 +00:00
|
|
|
#ifndef mingw32_HOST_OS
|
2012-08-03 14:45:18 +00:00
|
|
|
let at = if null hostname then "" else "@"
|
2012-10-25 22:17:32 +00:00
|
|
|
username <- liftIO myUserName
|
2012-08-03 14:45:18 +00:00
|
|
|
return $ concat [username, at, hostname, ":", reldir]
|
2013-05-11 20:03:00 +00:00
|
|
|
#else
|
|
|
|
return $ concat [hostname, ":", reldir]
|
|
|
|
#endif
|
2012-08-03 14:45:18 +00:00
|
|
|
|
2011-11-07 20:13:06 +00:00
|
|
|
initialize :: Maybe String -> Annex ()
|
|
|
|
initialize mdescription = do
|
2011-08-17 18:14:43 +00:00
|
|
|
prepUUID
|
2014-04-16 00:13:35 +00:00
|
|
|
initialize'
|
|
|
|
|
|
|
|
u <- getUUID
|
|
|
|
{- This will make the first commit to git, so ensure git is set up
|
|
|
|
- properly to allow commits when running it. -}
|
|
|
|
ensureCommit $ do
|
|
|
|
Annex.Branch.create
|
|
|
|
describeUUID u =<< genDescription mdescription
|
|
|
|
|
2014-09-05 17:44:09 +00:00
|
|
|
-- Everything except for uuid setup.
|
2014-04-16 00:13:35 +00:00
|
|
|
initialize' :: Annex ()
|
|
|
|
initialize' = do
|
2013-04-04 17:14:55 +00:00
|
|
|
checkFifoSupport
|
work around lack of receive.denyCurrentBranch in direct mode
Now that direct mode sets core.bare=true, git's normal prohibition about
pushing into the currently checked out branch doesn't work.
A simple fix for this would be an update hook which blocks the pushes..
but git hooks must be executable, and git-annex needs to be usable on eg,
FAT, which lacks x bits.
Instead, enabling direct mode switches the branch (eg master) to a special
purpose branch (eg annex/direct/master). This branch is not pushed when
syncing; instead any changes that git annex sync commits get written to
master, and it's pushed (along with synced/master) to the remote.
Note that initialization has been changed to always call setDirect,
even if it's just setDirect False for indirect mode. This is needed because
if the user has just cloned a direct mode repo, that nothing has synced
with before, it may have no master branch, and only a annex/direct/master.
Resulting in that branch being checked out locally too. Calling setDirect False
for indirect mode moves back out of this branch, to a new master branch,
and ensures that a manual "git push" doesn't push changes directly to
the annex/direct/master of the remote. (It's possible that the user
makes a commit w/o using git-annex and pushes it, but nothing I can do
about that really.)
This commit was sponsored by Jonathan Harrington.
2013-11-06 01:08:31 +00:00
|
|
|
checkCrippledFileSystem
|
|
|
|
unlessM isBare $
|
2013-11-05 19:29:56 +00:00
|
|
|
hookWrite preCommitHook
|
2013-12-29 17:06:23 +00:00
|
|
|
setVersion supportedVersion
|
work around lack of receive.denyCurrentBranch in direct mode
Now that direct mode sets core.bare=true, git's normal prohibition about
pushing into the currently checked out branch doesn't work.
A simple fix for this would be an update hook which blocks the pushes..
but git hooks must be executable, and git-annex needs to be usable on eg,
FAT, which lacks x bits.
Instead, enabling direct mode switches the branch (eg master) to a special
purpose branch (eg annex/direct/master). This branch is not pushed when
syncing; instead any changes that git annex sync commits get written to
master, and it's pushed (along with synced/master) to the remote.
Note that initialization has been changed to always call setDirect,
even if it's just setDirect False for indirect mode. This is needed because
if the user has just cloned a direct mode repo, that nothing has synced
with before, it may have no master branch, and only a annex/direct/master.
Resulting in that branch being checked out locally too. Calling setDirect False
for indirect mode moves back out of this branch, to a new master branch,
and ensures that a manual "git push" doesn't push changes directly to
the annex/direct/master of the remote. (It's possible that the user
makes a commit w/o using git-annex and pushes it, but nothing I can do
about that really.)
This commit was sponsored by Jonathan Harrington.
2013-11-06 01:08:31 +00:00
|
|
|
ifM (crippledFileSystem <&&> not <$> isBare)
|
|
|
|
( do
|
|
|
|
enableDirectMode
|
|
|
|
setDirect True
|
2014-02-11 04:39:50 +00:00
|
|
|
-- Handle case where this repo was cloned from a
|
|
|
|
-- direct mode repo
|
|
|
|
, unlessM isBare
|
|
|
|
switchHEADBack
|
work around lack of receive.denyCurrentBranch in direct mode
Now that direct mode sets core.bare=true, git's normal prohibition about
pushing into the currently checked out branch doesn't work.
A simple fix for this would be an update hook which blocks the pushes..
but git hooks must be executable, and git-annex needs to be usable on eg,
FAT, which lacks x bits.
Instead, enabling direct mode switches the branch (eg master) to a special
purpose branch (eg annex/direct/master). This branch is not pushed when
syncing; instead any changes that git annex sync commits get written to
master, and it's pushed (along with synced/master) to the remote.
Note that initialization has been changed to always call setDirect,
even if it's just setDirect False for indirect mode. This is needed because
if the user has just cloned a direct mode repo, that nothing has synced
with before, it may have no master branch, and only a annex/direct/master.
Resulting in that branch being checked out locally too. Calling setDirect False
for indirect mode moves back out of this branch, to a new master branch,
and ensures that a manual "git push" doesn't push changes directly to
the annex/direct/master of the remote. (It's possible that the user
makes a commit w/o using git-annex and pushes it, but nothing I can do
about that really.)
This commit was sponsored by Jonathan Harrington.
2013-11-06 01:08:31 +00:00
|
|
|
)
|
2013-02-20 17:55:53 +00:00
|
|
|
createInodeSentinalFile
|
2014-09-05 17:44:09 +00:00
|
|
|
checkSharedClone
|
2011-08-17 18:14:43 +00:00
|
|
|
|
|
|
|
uninitialize :: Annex ()
|
2012-04-27 16:21:38 +00:00
|
|
|
uninitialize = do
|
2013-11-05 19:29:56 +00:00
|
|
|
hookUnWrite preCommitHook
|
2012-04-27 16:21:38 +00:00
|
|
|
removeRepoUUID
|
2012-10-07 20:04:03 +00:00
|
|
|
removeVersion
|
2011-08-17 18:14:43 +00:00
|
|
|
|
2011-08-17 22:38:26 +00:00
|
|
|
{- Will automatically initialize if there is already a git-annex
|
2012-12-13 04:45:27 +00:00
|
|
|
- branch from somewhere. Otherwise, require a manual init
|
|
|
|
- to avoid git-annex accidentially being run in git
|
2013-11-05 20:42:59 +00:00
|
|
|
- repos that did not intend to use it.
|
|
|
|
-
|
|
|
|
- Checks repository version and handles upgrades too.
|
|
|
|
-}
|
2011-08-17 22:38:26 +00:00
|
|
|
ensureInitialized :: Annex ()
|
2014-11-04 22:04:19 +00:00
|
|
|
ensureInitialized = getVersion >>= maybe needsinit checkUpgrade
|
2012-10-29 01:27:15 +00:00
|
|
|
where
|
|
|
|
needsinit = ifM Annex.Branch.hasSibling
|
|
|
|
( initialize Nothing
|
|
|
|
, error "First run: git-annex init"
|
|
|
|
)
|
2011-08-17 18:36:20 +00:00
|
|
|
|
2012-07-31 20:19:24 +00:00
|
|
|
{- Checks if a repository is initialized. Does not check version for ugrade. -}
|
|
|
|
isInitialized :: Annex Bool
|
|
|
|
isInitialized = maybe Annex.Branch.hasSibling (const $ return True) =<< getVersion
|
|
|
|
|
work around lack of receive.denyCurrentBranch in direct mode
Now that direct mode sets core.bare=true, git's normal prohibition about
pushing into the currently checked out branch doesn't work.
A simple fix for this would be an update hook which blocks the pushes..
but git hooks must be executable, and git-annex needs to be usable on eg,
FAT, which lacks x bits.
Instead, enabling direct mode switches the branch (eg master) to a special
purpose branch (eg annex/direct/master). This branch is not pushed when
syncing; instead any changes that git annex sync commits get written to
master, and it's pushed (along with synced/master) to the remote.
Note that initialization has been changed to always call setDirect,
even if it's just setDirect False for indirect mode. This is needed because
if the user has just cloned a direct mode repo, that nothing has synced
with before, it may have no master branch, and only a annex/direct/master.
Resulting in that branch being checked out locally too. Calling setDirect False
for indirect mode moves back out of this branch, to a new master branch,
and ensures that a manual "git push" doesn't push changes directly to
the annex/direct/master of the remote. (It's possible that the user
makes a commit w/o using git-annex and pushes it, but nothing I can do
about that really.)
This commit was sponsored by Jonathan Harrington.
2013-11-06 01:08:31 +00:00
|
|
|
isBare :: Annex Bool
|
|
|
|
isBare = fromRepo Git.repoIsLocalBare
|
2011-08-17 22:52:58 +00:00
|
|
|
|
2013-05-14 00:48:44 +00:00
|
|
|
{- A crippled filesystem is one that does not allow making symlinks,
|
|
|
|
- or removing write access from files. -}
|
2013-02-15 18:17:31 +00:00
|
|
|
probeCrippledFileSystem :: Annex Bool
|
2013-02-14 18:10:36 +00:00
|
|
|
probeCrippledFileSystem = do
|
2013-08-04 17:07:55 +00:00
|
|
|
#ifdef mingw32_HOST_OS
|
2013-05-11 20:03:00 +00:00
|
|
|
return True
|
|
|
|
#else
|
2014-02-26 20:52:56 +00:00
|
|
|
tmp <- fromRepo gitAnnexTmpMiscDir
|
2013-02-15 18:17:31 +00:00
|
|
|
let f = tmp </> "gaprobe"
|
2013-11-18 22:20:20 +00:00
|
|
|
createAnnexDirectory tmp
|
|
|
|
liftIO $ writeFile f ""
|
2013-02-15 18:17:31 +00:00
|
|
|
uncrippled <- liftIO $ probe f
|
2013-02-14 18:10:36 +00:00
|
|
|
liftIO $ removeFile f
|
2013-02-15 18:17:31 +00:00
|
|
|
return $ not uncrippled
|
2013-02-14 18:10:36 +00:00
|
|
|
where
|
|
|
|
probe f = catchBoolIO $ do
|
|
|
|
let f2 = f ++ "2"
|
|
|
|
nukeFile f2
|
|
|
|
createSymbolicLink f f2
|
|
|
|
nukeFile f2
|
|
|
|
preventWrite f
|
|
|
|
allowWrite f
|
|
|
|
return True
|
2013-05-11 20:03:00 +00:00
|
|
|
#endif
|
2013-02-15 18:17:31 +00:00
|
|
|
|
|
|
|
checkCrippledFileSystem :: Annex ()
|
2013-04-03 07:52:41 +00:00
|
|
|
checkCrippledFileSystem = whenM probeCrippledFileSystem $ do
|
2013-02-15 22:16:50 +00:00
|
|
|
warning "Detected a crippled filesystem."
|
2013-02-15 18:17:31 +00:00
|
|
|
setCrippledFileSystem True
|
2013-05-14 00:48:44 +00:00
|
|
|
|
work around lack of receive.denyCurrentBranch in direct mode
Now that direct mode sets core.bare=true, git's normal prohibition about
pushing into the currently checked out branch doesn't work.
A simple fix for this would be an update hook which blocks the pushes..
but git hooks must be executable, and git-annex needs to be usable on eg,
FAT, which lacks x bits.
Instead, enabling direct mode switches the branch (eg master) to a special
purpose branch (eg annex/direct/master). This branch is not pushed when
syncing; instead any changes that git annex sync commits get written to
master, and it's pushed (along with synced/master) to the remote.
Note that initialization has been changed to always call setDirect,
even if it's just setDirect False for indirect mode. This is needed because
if the user has just cloned a direct mode repo, that nothing has synced
with before, it may have no master branch, and only a annex/direct/master.
Resulting in that branch being checked out locally too. Calling setDirect False
for indirect mode moves back out of this branch, to a new master branch,
and ensures that a manual "git push" doesn't push changes directly to
the annex/direct/master of the remote. (It's possible that the user
makes a commit w/o using git-annex and pushes it, but nothing I can do
about that really.)
This commit was sponsored by Jonathan Harrington.
2013-11-06 01:08:31 +00:00
|
|
|
{- Normally git disables core.symlinks itself when the
|
|
|
|
- filesystem does not support them, but in Cygwin, git
|
|
|
|
- does support symlinks, while git-annex, not linking
|
|
|
|
- with Cygwin, does not. -}
|
2013-05-14 18:18:34 +00:00
|
|
|
whenM (coreSymlinks <$> Annex.getGitConfig) $ do
|
|
|
|
warning "Disabling core.symlinks."
|
|
|
|
setConfig (ConfigKey "core.symlinks")
|
|
|
|
(Git.Config.boolConfig False)
|
|
|
|
|
2013-04-04 17:14:55 +00:00
|
|
|
probeFifoSupport :: Annex Bool
|
|
|
|
probeFifoSupport = do
|
2013-08-04 17:07:55 +00:00
|
|
|
#ifdef mingw32_HOST_OS
|
2013-05-11 20:03:00 +00:00
|
|
|
return False
|
|
|
|
#else
|
2014-02-26 20:52:56 +00:00
|
|
|
tmp <- fromRepo gitAnnexTmpMiscDir
|
2013-04-04 17:14:55 +00:00
|
|
|
let f = tmp </> "gaprobe"
|
2013-11-18 22:20:20 +00:00
|
|
|
createAnnexDirectory tmp
|
2013-04-04 17:14:55 +00:00
|
|
|
liftIO $ do
|
|
|
|
nukeFile f
|
2013-04-04 18:25:20 +00:00
|
|
|
ms <- tryIO $ do
|
|
|
|
createNamedPipe f ownerReadMode
|
|
|
|
getFileStatus f
|
2013-04-04 17:14:55 +00:00
|
|
|
nukeFile f
|
|
|
|
return $ either (const False) isNamedPipe ms
|
2013-05-11 20:03:00 +00:00
|
|
|
#endif
|
2013-04-04 17:14:55 +00:00
|
|
|
|
|
|
|
checkFifoSupport :: Annex ()
|
|
|
|
checkFifoSupport = unlessM probeFifoSupport $ do
|
|
|
|
warning "Detected a filesystem without fifo support."
|
|
|
|
warning "Disabling ssh connection caching."
|
|
|
|
setConfig (annexConfig "sshcaching") (Git.Config.boolConfig False)
|
work around lack of receive.denyCurrentBranch in direct mode
Now that direct mode sets core.bare=true, git's normal prohibition about
pushing into the currently checked out branch doesn't work.
A simple fix for this would be an update hook which blocks the pushes..
but git hooks must be executable, and git-annex needs to be usable on eg,
FAT, which lacks x bits.
Instead, enabling direct mode switches the branch (eg master) to a special
purpose branch (eg annex/direct/master). This branch is not pushed when
syncing; instead any changes that git annex sync commits get written to
master, and it's pushed (along with synced/master) to the remote.
Note that initialization has been changed to always call setDirect,
even if it's just setDirect False for indirect mode. This is needed because
if the user has just cloned a direct mode repo, that nothing has synced
with before, it may have no master branch, and only a annex/direct/master.
Resulting in that branch being checked out locally too. Calling setDirect False
for indirect mode moves back out of this branch, to a new master branch,
and ensures that a manual "git push" doesn't push changes directly to
the annex/direct/master of the remote. (It's possible that the user
makes a commit w/o using git-annex and pushes it, but nothing I can do
about that really.)
This commit was sponsored by Jonathan Harrington.
2013-11-06 01:08:31 +00:00
|
|
|
|
|
|
|
enableDirectMode :: Annex ()
|
|
|
|
enableDirectMode = unlessM isDirect $ do
|
|
|
|
warning "Enabling direct mode."
|
|
|
|
top <- fromRepo Git.repoPath
|
|
|
|
(l, clean) <- inRepo $ Git.LsFiles.inRepo [top]
|
|
|
|
forM_ l $ \f ->
|
|
|
|
maybe noop (`toDirect` f) =<< isAnnexLink f
|
|
|
|
void $ liftIO clean
|
2013-12-02 16:34:16 +00:00
|
|
|
|
2014-09-05 17:44:09 +00:00
|
|
|
checkSharedClone :: Annex ()
|
|
|
|
checkSharedClone = whenM (inRepo Git.Objects.isSharedClone) $ do
|
|
|
|
showSideAction "Repository was cloned with --shared; setting annex.hardlink=true and making repository untrusted."
|
|
|
|
u <- getUUID
|
|
|
|
trustSet u UnTrusted
|
|
|
|
setConfig (annexConfig "hardlink") (Git.Config.boolConfig True)
|