Sudo - Revision history

Bech: corrections

2018-05-03T12:52:51Z

corrections

Bech at 12:43, 3 May 2018

2018-05-03T12:43:11Z

Unhammer at 08:20, 19 March 2018

2018-03-19T08:20:03Z

Unhammer at 08:19, 19 March 2018

2018-03-19T08:19:55Z

Unhammer: advice

2018-03-19T08:18:40Z

advice

New page

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.

@@ Line 1: / Line 1: @@
 <!--  ಠ_ಠ -->
-If you're working on language data, <code>sudo<code> is pretty much only for running package managers like <code>apt</code> (or <code>port</code> or <code>dnf</code>) and for running package setup scripts like https://apertium.projectjj.com/apt/install-nightly.sh
+If you're working on language data, <code>sudo</code> is pretty much only for running package managers like <code>apt</code> (or <code>port</code> or <code>dnf</code>) and for running package setup scripts like https://apertium.projectjj.com/apt/install-nightly.sh
 In general, '''don't use <code>sudo</code> (and don't run as the root user) when building/compiling things'''
@@ Line 7: / Line 7: @@
 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.
+But if you work on your own computer, a possibility is to allow the instalation directory (generally <code>/usr/local/share</code>) a write access from your account (using <code>chown, chgrp</code> or <code>chmod</code> with <code>sudo</code>), and then, you will not have to use <code>sudo</code> any more for compiling a language pair.

← Older revision		Revision as of 12:43, 3 May 2018
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.

← Older revision		Revision as of 08:20, 19 March 2018
Line 1:		Line 1:
	<!-- ಠ_ಠ -- >		<!-- ಠ_ಠ -->

	If you're working on language data, <code>sudo<code> is pretty much only for running package managers like <code>apt</code> (or <code>port</code> or <code>dnf</code>) and for running package setup scripts like https://apertium.projectjj.com/apt/install-nightly.sh		If you're working on language data, <code>sudo<code> is pretty much only for running package managers like <code>apt</code> (or <code>port</code> or <code>dnf</code>) and for running package setup scripts like https://apertium.projectjj.com/apt/install-nightly.sh

@@ Line 1: / Line 1: @@
+<!--  ಠ_ಠ -- >
-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
+If you're working on language data, <code>sudo<code> is pretty much only for running package managers like <code>apt</code> (or <code>port</code> or <code>dnf</code>) 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'''.
+In general, '''don't use <code>sudo</code> (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.
+The only exception is <code>sudo make install</code>, but when working on language data you should never have to do this.