New tool local language repositories #186
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a small tool I made for creating and maintaining manual language clones. I got tired of searching outside of
doc-base
for listings of languages that builds and publishes, that builds only revcheck, their cloning end points, and so on, to later include/use in other scripts. After a while, it grew into a complete tool for creating and maintaining local language repositories for editors and tool makers.Current usage:
Need a complete new checkout of all publishing languages for testing purposes? Git clone doc-base and do
php doc-base/languages.php --clone
. Boom, done.Also need the revchecking ones?
languages.php --clone --rev
. Need all repositories?languages.php --clone --all
.Has one set of clones that need pulling for a test?
languages.php --pull --all
. After a test, need to revert them to pristine state?languages.php --undo --all
. Two or three in particular?languages.php --undo --pull dir1 dir2 dir3
.Need to know what are the building languages?
languages.php --list-csv
. Space separated for shell scripts?languages.php --list-ssv
. And also use--all
/--rev
for listings beyond building publishing ones.Prefer to have this information as files, instead doing string path manipulations?
languages.php --mark
createsBUILDMAN
/BUILDREV
files that contain the respective language label as contents, so any new command can simple traverse all directories forlang/BUILDMAN
file existence.