Btukfyl

I created some rather big glossaries files with symbols, acronyms, ... for a programming project with multiple tex documents as their documentation. Each glossaries file is a single tex file for reuse throughout the multiple documents of the project. The document is part of a SVN repository. I created a single common directory to store files that are used in all tex documents throughout the repository. I managed to access this common directory by definition of

newcommand{commonpath}{../Common}

and added the paths to the single documents relatively using this path statement.

Now I want to write a new document as part of a another SVN repository and re-use the same glossaries files. I could of course copy the files to the new project. However, I want to keep one common "language" throughout all of my documents. Thus, I would rather work and change one single file at a single location rather than to keep multiple files synchronized. For my local installation I now the relative positioning of the two repositories and their tex documents with respect to each other. However, if a 3rd person checks out both SVN repositories, I cannot assure that they use the same relative path of the 2 repository checkouts.

How can I access the glossaries files from multiple projects? I am on Windows using MikTeX 2.9. Is there a possibility to make single tex files available throughout the system, e.g. via the directories path of the MikTeX Console? Or is it preferable to pack the files into a new package to deploy myself?

Can someone please give me some hints? What is the best way?

There are those much better qualified than me to answer, so feel free to accept a later answer however you asked for hints and there is perhaps too much for mere comments.

Your tags need changing to attract focused answers so I will alter some. It would also help if you describe your system architecture such as are all users one of Windows / Linux / Mac and are the files checked out from SVN via mapped drives etc. (beware mapped drives that have underlying spaces accents etc.)

Do all users use an IDE (which) or do some need command line compilation ?

How do you address auxdirs such as TEXINPUTS= since MiKTeX has a slightly different pathing structure compared to say TeX Live ?

Do you use xindy or only makeindex ?

Do you use command aggregation such as arara or latexmk ?

How do you handle build directories are all aux files in the same directory as the main.tex

Your specific query for glossaries is perhaps suited to section 7.3 in https://en.wikibooks.org/wiki/LaTeX/Glossary#Glossary_definitions

and for a related acronyms Question/Answer here
Create separate list of acronyms and glossary