Difference between revisions of "Sudo"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
The only exception is <code>sudo make install</code>, but when working on language data you should never have to do this. |
The only exception is <code>sudo make install</code>, but when working on language data you should never have to do this. |
||
But if you work on your own computer, a possibility is to allow the instalation directory (generally /usr/local/share) a write access from your account (using chown, chgrp or chmod with sudo), and then, you will not have to use sudo any more for compiling a language pair. |
|||
Revision as of 12:43, 3 May 2018
If you're working on language data, sudo is pretty much only for running package managers like apt (or port or dnf) and for running package setup scripts like https://apertium.projectjj.com/apt/install-nightly.sh
In general, don't use sudo (and don't run as the root user) when building/compiling things
The only exception is sudo make install, but when working on language data you should never have to do this.
But if you work on your own computer, a possibility is to allow the instalation directory (generally /usr/local/share) a write access from your account (using chown, chgrp or chmod with sudo), and then, you will not have to use sudo any more for compiling a language pair.
