Mercurial (hg) Installation Without Being Root - Versionsgeschichte

Andreas Plank: Hilfe:Kategorisieren von Seiten: Ergänze Kategorie:English pages

2022-08-25T19:08:13Z

Hilfe:Kategorisieren von Seiten: Ergänze Kategorie:English pages

Andreas Plank: Hilfe:Kategorisieren von Seiten: Ergänze Kategorie:Installationen

2022-08-25T19:07:34Z

Hilfe:Kategorisieren von Seiten: Ergänze Kategorie:Installationen

Jan R.B.-Wein: /* broken link What finally worked for us */

2014-01-14T11:44:31Z

broken link What finally worked for us

Jan R.B.-Wein: /* Fixed internal jumps - Now #jump instead of opening in a new tab. */

2014-01-14T11:42:52Z

Fixed internal jumps - Now #jump instead of opening in a new tab.

Jan R.B.-Wein: /* tried to resolve a bit of the mess in earlier chapters */

2014-01-14T11:35:16Z

tried to resolve a bit of the mess in earlier chapters

Jan R.B.-Wein: /* Better introduction, some explanation as to what chapter is relevant. */

2014-01-14T11:17:56Z

Better introduction, some explanation as to what chapter is relevant.

Jan R.B.-Wein: /* typo and thus heading error */

2014-01-14T11:02:48Z

typo and thus heading error

Jan R.B.-Wein: /* Added alternative solution for crating missing .bash* files. */

2014-01-14T11:01:27Z

Added alternative solution for crating missing .bash* files.

Jan R.B.-Wein: /* ' can't be escaped in bash commands ... so now " and ' are used for cascading. */

2014-01-14T10:57:41Z

' can't be escaped in bash commands ... so now " and ' are used for cascading.

Jan R.B.-Wein: /* Forgot several 'echo' in a bash command ... */

2014-01-14T10:51:47Z

Forgot several 'echo' in a bash command ...

← Abfassung vorher		Version vom 25. August 2022, 19:08 Uhr
Zeile 611:		Zeile 611:

	[[Kategorie:Installationen]]		[[Kategorie:Installationen]]
		+	[[Kategorie:English pages]]

← Abfassung vorher		Version vom 25. August 2022, 19:07 Uhr
Zeile 609:		Zeile 609:
	ln -s ~/hg ~/[Sub domain]		ln -s ~/hg ~/[Sub domain]
	-->		-->
		+
		+	[[Kategorie:Installationen]]

← Abfassung vorher		Version vom 14. Januar 2014, 11:44 Uhr
Zeile 4:		Zeile 4:
	In the following the process of how we got mercurial working on our webspace (we don't own a server due to financial reasons) is documented. A lot of special information is added in the second chapter that is nice to know, but as it turned out this did not work for us.		In the following the process of how we got mercurial working on our webspace (we don't own a server due to financial reasons) is documented. A lot of special information is added in the second chapter that is nice to know, but as it turned out this did not work for us.

−	So the only really relevant part is the Chapter: [[#~~What_finally_worked_for_us~~:\| ~~What~~ finally worked for us]]. If you want to know something about why the first undertakings did fail read all chapters, but I warn you, it's messy. Hence it's probably better to read the excerpt of [[#Problems_that_might_occur_.28and_occurred_for_me.29 \| problems that occurred]] for us instead.	+	So the only really relevant part is the Chapter: [[#Our_solution_.28what_we_ended_up_with.29:\| Our solution (what finally worked for us)]]. If you want to know something about why the first undertakings did fail read all chapters, but I warn you, it's messy. Hence it's probably better to read the excerpt of [[#Problems_that_might_occur_.28and_occurred_for_me.29 \| problems that occurred]] for us instead.

@@ Zeile 4: / Zeile 4: @@
 In the following the process of how we got mercurial working on our webspace (we don't own a server due to financial reasons) is documented. A lot of special information is added in the second chapter that is nice to know, but as it turned out this did not work for us.
-So the only really relevant part is the Chapter:  [http://wiki.opensourceecology.de/Mercurial_(hg)_Installation_Without_Being_Root#What_finally_worked_for_us: What finally worked for us]. If you want to know something about why the first undertakings did fail read all chapters, but I warn you, it's messy. Hence it's probably better to read the excerpt of [http://wiki.opensourceecology.de/Mercurial_(hg)_Installation_Without_Being_Root#Problems_that_might_occur_.28and_occurred_for_me.29 problems that occurred] for us instead.
+So the only really relevant part is the Chapter:  [[#What_finally_worked_for_us:| What finally worked for us]]. If you want to know something about why the first undertakings did fail read all chapters, but I warn you, it's messy. Hence it's probably better to read the excerpt of [[#Problems_that_might_occur_.28and_occurred_for_me.29 | problems that occurred]] for us instead.
@@ Zeile 20: / Zeile 20: @@
 Source: http://mercurial.selenic.com/wiki/UnixInstall#Per-user_installation
-Continue with Chapter: [http://wiki.opensourceecology.de/Mercurial_(hg)_Installation_Without_Being_Root#Configure_Mercurial_for_a_Python_installation: Configure Mercurial for a Python installation].
+Continue with Chapter: [[#Configure_Mercurial_for_a_Python_installation: | Configure Mercurial for a Python installation]].
@@ Zeile 44: / Zeile 44: @@
 <code>
-$ sudo apt-get install python2.7 python2.7-dev #if unmet dependencies problem occurs see [http://wiki.opensourceecology.de/Mercurial_%28hg%29_Installation_Without_Being_Root#Problems_that_might_occur_.28and_occurred_for_me.29 below]
+$ sudo apt-get install python2.7 python2.7-dev #if unmet dependencies problem occurs see [[#Problems_that_might_occur_.28and_occurred_for_me.29 | below]]
 </code>
@@ Zeile 222: / Zeile 222: @@
 <code>
-$ scp ~/mercurial-2.8.tar.gz ftp118002-2629078@dragontale.de:mercurial-2.8.tar.gz
+$ scp ~/mercurial-2.8.tar.gz <user>@<server>:mercurial-2.8.tar.gz
 </code>
@@ Zeile 268: / Zeile 268: @@
-Now continue with Sub-Chapter: [http://wiki.opensourceecology.de/Mercurial_(hg)_Installation_Without_Being_Root#Resume_Mercurial_installation. Make Python and Mercurial commands available (ease of use)].
+Now continue with Sub-Chapter: [[#Resume_Mercurial_installation. | Make Python and Mercurial commands available (ease of use)]].

@@ Zeile 4: / Zeile 4: @@
 In the following the process of how we got mercurial working on our webspace (we don't own a server due to financial reasons) is documented. A lot of special information is added in the second chapter that is nice to know, but as it turned out this did not work for us.
-So the only really relevant part is the Chapter:  [wiki.opensourceecology.de/Mercurial_(hg)_Installation_Without_Being_Root#What_finally_worked_for_us: What finally worked for us]. If you want to know something about why the first undertakings did fail read all chapters, but I warn you, it's messy. Hence it's probably better to read the excerpt of [#Problems_that_might_occur_.28and_occurred_for_me.29 problems that occurred] for us instead.
+So the only really relevant part is the Chapter:  [http://wiki.opensourceecology.de/Mercurial_(hg)_Installation_Without_Being_Root#What_finally_worked_for_us: What finally worked for us]. If you want to know something about why the first undertakings did fail read all chapters, but I warn you, it's messy. Hence it's probably better to read the excerpt of [http://wiki.opensourceecology.de/Mercurial_(hg)_Installation_Without_Being_Root#Problems_that_might_occur_.28and_occurred_for_me.29 problems that occurred] for us instead.
@@ Zeile 19: / Zeile 19: @@
 Source: http://mercurial.selenic.com/wiki/UnixInstall#Per-user_installation
@@ Zeile 24: / Zeile 26: @@
 To install mercurial without being root, needs us to bundle Python 2.x (as Python 3 is not yet supported as there is only one advantage in favour of upgrading, so it's not worth the effort currently).
 ===Windows===
-For Windows there currently is PortablePython as a ready made option.
+For Windows there currently is PortablePython as a ready made option. But you have to ensure that the header python-dev files are available. Otherwise it will not work. We have not tested this route as we consider Linux (Open source & non-profit, btw Mac OS is also essentially Linux, just like Android) our friend while Windows (Closed source & commercial) as our ... well, is enemy the correct word? I don't know.
 ===UNIX/POSIX===
@@ Zeile 212: / Zeile 215: @@
-==Configure Mercurial for a Python installation or PortablePython:==
+==Configure Mercurial for a Python installation:==
 <code>
@@ Zeile 232: / Zeile 235: @@
 Unpack the downloaded mercurial package:
 <code>
 $ tar -xzf mercurial-2.8.tar.gz --directory mercurial    # -C is a synonym=alias for --directory
 </code>
 <code>
@@ Zeile 265: / Zeile 266: @@
 $ ./hg --version  # should show the latest version
 </code>
@@ Zeile 306: / Zeile 310: @@
 <!-- WORKING SOLUTION -->
-==What finally worked for us;==
+==Our solution (what we ended up with):==

@@ Zeile 1: / Zeile 1: @@
-Solutions for installing mercurial from a package repository or via a self-extracting or any other installer for all operating system distribution can easily be found. So this is not the topic of thise Wiki entry. Here we cover the installation of a mercurial versioning system without root access. It is a necessary step for the creation of our synergetic hard and software development system that at a later point shall be mirrored by the Wiki to keep it up to date and to keep development efforts bundled in our versioning system (mercurial, git, svn, bzr, ...).
+Solutions for installing mercurial from a package repository or via a self-extracting or any other installer can easily be found for all operating system distributions. Thus this is not the topic of this Wiki entry. Here we cover the installation of a mercurial versioning system '''without root access'''. It is a necessary step for the creation of our symbiotic open source hard and software development system that at a later point shall be mirrored by the Wiki to keep it up to date automatically and at all times. This allows us to bundle our efforts for development in our versioning system (I use mercurial, but git, svn, bzr, ... will be fine too).
 ==With a Python installation readily available or with rights to install a python environment:==
-If a python installation is available or you have a server where you have adminsitrative rights for installing the python and still want to have a local installation of mercurial into your home directory, this also is no problem by using the Mercurial script: make install-home (to include documentation) or make install-home-bin (for the executable only). If you used a custom python location for the script it is required to add the following to the command to communicate it to hg:
+It's also no problem, if a python installation is available or you have a server where you have adminsitrative rights (root access) for installing a python environment and still want to have a local installation of mercurial into your home directory. It is recomended to use the Mercurial script: ''make install-home'' (to include documentation) or ''make install-home-bin'' (for the executable only). If you used a custom python location for the script it is required to add the following to the command to communicate it to hg:
 <code>
@@ Zeile 301: / Zeile 305: @@
-<!-- WORKING SOLUTIN -->
+<!-- WORKING SOLUTION -->
-==Working solution==
+==What finally worked for us;==

@@ Zeile 129: / Zeile 129: @@
-===Avoid this: Bundle Mercurial and Python===
+====Avoid this: Bundle Mercurial and Python====
 This is only required if no compiler on target host/server and if using make install-home-bin is impossible and all other <code>make install</code> fail.
@@ Zeile 467: / Zeile 467: @@
-====Create alias:===
+====Create alias:====
 <code>
 $ echo "alias python='~/bin/python'" >> ~/.bashrc && echo "alias python='~/bin/python'" >> ~/.bash_profile && echo "alias hg='~/bin/hg'" >> ~/.bashrc && echo "alias hg='~/bin/hg'" >> ~/.bash_profile

@@ Zeile 455: / Zeile 455: @@
 As the target server probably does have another installation of python in /usr/bin we want to overwrite the python command to automatically use the correct one [the one we installed ourselves]. So we append an alias to the .bashrc and .bash_profile that should get executed on ssh login too. Also we make the hg command available in our <code>$HOME</code> directory and all directories below included.
 If the files .bashrc and .bash_profile don't exist yet in <code>$HOME</code> directory - check it via <code>ls -a $HOME</code> - then use <code>vi ~/.bashrc</code> and type 'i' key for insert mode and insert <code>#!/bin/sh</code>. Then leave the Insert mode via <code>ESC</code> and save the file by typing <code>:wq</code>.
 <code>
 $ echo "alias python='~/bin/python'" >> ~/.bashrc && echo "alias python='~/bin/python'" >> ~/.bash_profile && echo "alias hg='~/bin/hg'" >> ~/.bashrc && echo "alias hg='~/bin/hg'" >> ~/.bash_profile

@@ Zeile 450: / Zeile 450: @@
 As the target server probably does have another installation of python in /usr/bin we want to overwrite the python command to automatically use the correct one [the one we installed ourselves]. So we append an alias to the .bashrc and .bash_profile that should get executed on ssh login too. Also we make the hg command available in our <code>$HOME</code> directory and all directories below included.
@@ Zeile 456: / Zeile 458: @@
 <code>
-$ echo 'alias python=\'~/bin/python\'' >> ~/.bashrc && echo 'alias python=\'~/bin/python\'' >> ~/.bash_profile && echo 'alias hg=\'~/bin/hg\'' >> ~/.bashrc && echo 'alias hg=\'~/bin/hg\'' >> ~/.bash_profile
+$ echo "alias python='~/bin/python'" >> ~/.bashrc && echo "alias python='~/bin/python'" >> ~/.bash_profile && echo "alias hg='~/bin/hg'" >> ~/.bashrc && echo "alias hg='~/bin/hg'" >> ~/.bash_profile
 </code>

@@ Zeile 433: / Zeile 433: @@
 <code>
 $ cd ~/python-dev/ && make altinstall prefix=$HOME exec-prefix=$HOME
 </code>
@@ Zeile 445: / Zeile 449: @@
 </code>
@@ Zeile 455: / Zeile 456: @@
 <code>
-$ 'alias python=\'~/bin/python\'' >> ~/.bashrc && 'alias python=\'~/bin/python\'' >> ~/.bash_profile && 'alias hg=\'~/bin/hg\'' >> ~/.bashrc && 'alias hg=\'~/bin/hg\'' >> ~/.bash_profile
+$ echo 'alias python=\'~/bin/python\'' >> ~/.bashrc && echo 'alias python=\'~/bin/python\'' >> ~/.bash_profile && echo 'alias hg=\'~/bin/hg\'' >> ~/.bashrc && echo 'alias hg=\'~/bin/hg\'' >> ~/.bash_profile
 </code>