Skip to content

Latest commit

 

History

History
61 lines (38 loc) · 2.27 KB

README.md

File metadata and controls

61 lines (38 loc) · 2.27 KB

Please Note:

Creating/Editing Catalog Files

For information on naming descriptors, and the encoding to use - please see the Wiki

Adding the Catalog Submodules

The proccess for adding a new catalog-translation submodule to the main AROS respository, aswell as the translations repository is the same.

If the original catalogs where located at e.g 'workbench/tools/"my_tool"/catalogs', you should firstly create a repository called "my_tool" in the translation team organization. Use this to store the actual catalog descriptors, and mmakefile.src to create the catalogs.

Once the "my tool" repository is set up, add it to the main repositories as follows -:

  • cd "repository path"
  • cd "path to location the submodule should be attached under"

In our example case this would be 'cd workbench/tools/"my_tool"'.

Finaly commit and push the changes.

Updating the Submodules

To synchronise the repository with the individual catalog submodules, first checkout the modules repository and find out the current HEAD's sha1 -:

  • cd "module path"
  • git rev-list HEAD

Then update the translations repository, first checking the mode using ls-files

  • cd "translations path"
  • git ls-files --stage "submodule path"
  • git update-index --cacheinfo "mode from ls-files","sha1 commit id from module","submodule path"

e.g.

  • git update-index --cacheinfo 160000,03d7dff560ac8ed64f16e763204b04ce91ca5faf,workbench/system/AboutAROS/catalogs

Finaly commit and push the changes. Repeat this process for the submodules in the main AROS repository.

Updating the AROS Developer mirror

to push changes from the translation teams repository, to the official developer team mirror, please do the following...

Initial Setup:

Push changes in the Mirror:

  • git fetch -p origin
  • git push --mirror