| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| howto:configure [2014/01/03 15:45] – external edit 127.0.0.1 | howto:configure [2019/01/25 16:02] – ↷ Links adapted because of a move operation oroehrig |
|---|
| ====== Configuring polymake for a group of users ====== | ====== Configuring polymake for a group of users ====== |
| |
| Let's suppose you want to share your polymake installation with your colleagues or to prepare it for students in your class. First of all, you have to choose an installation location accessible from all computers in your lab (for example, an NFS or Samba share), and pass it to the [[install#configuration|build configuration]] script. After having completed the installation by calling ''make install'', you'll surely be curious to see whether it works at all. You'll start it, do some little exercises, and probably check for additional software you might need. To get the first overview, use the commands ''show_credits'' and ''show_unconfigured'' . Then, if you miss something, you'll install it - again, at some commonly accessible location - and [[:general#configuration|reconfigure]] the corresponding polymake interfaces. You might also want to add some [[reference:extensions]] to your installation and configure them as well. | Let's suppose you want to share your polymake installation with your colleagues or to prepare it for students in your class. First of all, you have to choose an installation location accessible from all computers in your lab (for example, an NFS or Samba share), and pass it to the [[install#configuration|build configuration]] script. After having completed the installation by calling ''make install'', you'll surely be curious to see whether it works at all. You'll start it, do some little exercises, and probably check for additional software you might need. To get the first overview, use the commands ''show_credits'' and ''show_unconfigured'' . Then, if you miss something, you'll install it - again, at some commonly accessible location - and [[:general#configuration|reconfigure]] the corresponding polymake interfaces. You might also want to add some [[user_guide:extend:extensions]] to your installation and configure them as well. |
| |
| Now everything is ready to be published - but anyone else starting to work with your installation will have to repeat all the configuration steps you've already made. You'll have to write down detailed instructions and hand them out to each new user. Moreover, if you decide to add some external software component or an extension later, you'll have to notify all your co-workers once again. Isn't it tedious? | Now everything is ready to be published - but anyone else starting to work with your installation will have to repeat all the configuration steps you've already made. You'll have to write down detailed instructions and hand them out to each new user. Moreover, if you decide to add some external software component or an extension later, you'll have to notify all your co-workers once again. Isn't it tedious? |
| The configuration path may consist of several global files if needed, separated by semicolon. The trailing element ''user'' allows the user to store his individual settings permanently in the directory ''~/.polymake''; alternative location may be specified in the environment variable ''POLYMAKE_USER_DIR'' or by putting ''user=~/other/path'' as the trailing element of the configuration path. | The configuration path may consist of several global files if needed, separated by semicolon. The trailing element ''user'' allows the user to store his individual settings permanently in the directory ''~/.polymake''; alternative location may be specified in the environment variable ''POLYMAKE_USER_DIR'' or by putting ''user=~/other/path'' as the trailing element of the configuration path. |
| |
| If the private directory is omitted in the configuration path, the user won't be able to save his private settings between the sessions (the interactive shell input history won't be stored either). This setup might be appropriate for a teaching lab where several students share the same login account. Another sensible use case for this mode is when polymake is called from a program linked with its [[reference:callable|callable library]]. Since the users of such a program doesn't see polymake directly, there might be a good reason for hindering polymake to leave any traces in the user's home directory. | If the private directory is omitted in the configuration path, the user won't be able to save his private settings between the sessions (the interactive shell input history won't be stored either). This setup might be appropriate for a teaching lab where several students share the same login account. Another sensible use case for this mode is when polymake is called from a program linked with its [[:callable|callable library]]. Since the users of such a program doesn't see polymake directly, there might be a good reason for hindering polymake to leave any traces in the user's home directory. |
| |
| The elements of the configuration path may start with ''~/'', designating the user's home directory, or refer to other environment variables using usual syntax ''$NAME''. | The elements of the configuration path may start with ''~/'', designating the user's home directory, or refer to other environment variables using usual syntax ''$NAME''. |