version control - How to maintain a small repository of bash/python scripts -
for past several years, i've been making small (single file, 1-500 line) scripts (mostly bash & python) automate random tasks (usually scientific data analysis). of these end being one-offs, want go , revisit/change something, or end rather unwieldy script benefit sort of version control. should note of these scripts done solely on own, , don't need share-able.
which type of versioning (svn,cvs,git,mercurial..) has simplest command structure/syntax use case? more importantly, machines connect behind rather finicky kerberos walls, i'm not looking sophisticated server-based implementation.
i found this thread 2010 asking similar question, though didn't talk specific options, whether or not should using single repository.
in short, versioning system allows simple same-directory approach minimal bells & whistles (only checkouts , commits needed)?
should set sort of subversion/cvs/git repository , throw in?
yes.
for use-case, suppose, svn can best choice (with url-based access every object in repo can easy , fast access single file revision of file , linear history "not best" merge in svn isn't problem). local file:///-based repository require minimum of maintenance. can use single-repository, flat tree (all files in /trunk)
Comments
Post a Comment