|
|
|
|
|
A good page to quickly understand the way Mercurial work should be read [here](http://www.selenic.com/mercurial/wiki/UnderstandingMercurial)
|
|
|
A good page to quickly understand the way GIT work should be read [here](https://git-scm.com/book/en/v2/Getting-Started-Git-Basics)
|
|
|
|
|
|
*Set certificate fingerprint*:
|
|
|
Add the folowing fingerprint for server hg.gajim.org into the `~/.hgrc` Mercurial configuration file.
|
|
|
|
|
|
[hostfingerprints]
|
|
|
hg.gajim.org = 46:E2:A5:E5:85:2A:5F:98:10:E5:78:FB:15:0C:FE:F0:93:A7:D9:E6
|
|
|
*Initial code checkout*:
|
|
|
|
|
|
hg clone https://hg.gajim.org/gajim gajim
|
|
|
*Updating to current version* (Be careful: -C option revert your local changes):
|
|
|
git clone https://dev.gajim.org/gajim/gajim.git
|
|
|
|
|
|
*Updating to current version*:
|
|
|
|
|
|
cd gajim && git pull
|
|
|
|
|
|
cd gajim && hg pull && hg up -C
|
|
|
*Launching*:
|
|
|
|
|
|
cd gajim
|
|
|
./launch.sh
|
|
|
|
|
|
Nightly builds can be found [here](https://gajim.org/downloads.php?#snaps) and [there (deb)](https://gajim.org/downloads.php?#debian)
|
|
|
Nightly builds can be found [here](https://gajim.org/downloads/snap) and [there (deb)](https://gajim.org/downloads.php?#debian)
|
|
|
|
|
|
*Running bleeding edge Gajim and python-nbxmpp together*
|
|
|
|
|
|
One on the dependencies ([python-nbxmpp library](https://python-nbxmpp.gajim.org)) is developed in-house. If you want to always use the latest version of python-nbxmpp without installing it every time, you can do it like this:
|
|
|
One of the dependencies ([python-nbxmpp library](https://dev.gajim.org/gajim/python-nbxmpp)) is developed in-house. If you want to always use the latest version of python-nbxmpp without installing it every time, you can do it like this:
|
|
|
|
|
|
PYTHONPATH=/an/absolute/path/to/python-nbxmpp/ ./launch.sh
|
|
|
|
|
|
|
|
|
## Mixing HG and Stable
|
|
|
If you run hg and then you go back to a stable version you will have problems, because the stable version cannot understand the new config. So if you have done that you need to clean you config and create a new one. First, close all Gajim instances and then
|
|
|
## Mixing GIT and Stable
|
|
|
If you run git and then you go back to a stable version you will have problems, because the stable version cannot understand the new config. So if you have done that you need to clean you config and create a new one. First, close all Gajim instances and then
|
|
|
|
|
|
* In GNU/Linux
|
|
|
|
|
|
|
|
|
rm ~/.gajim/config
|
|
|
|
|
|
* In Windows 2000/XP
|
... | ... | @@ -48,34 +44,12 @@ now locate the config file and remove it |
|
|
Now launch the application and a new config file will be created (you need to set accounts and other settings from scratch)
|
|
|
|
|
|
|
|
|
### Running both: Stable and HG
|
|
|
### Running both: Stable and GIT
|
|
|
|
|
|
OK. That is also possible but you should avoid mixing the config file.
|
|
|
|
|
|
* In GNU/Linux
|
|
|
|
|
|
./launch.sh -p git -s
|
|
|
|
|
|
./launch.sh -p hg
|
|
|
|
|
|
this creates a config.hg (eg profile hg)
|
|
|
|
|
|
''I've made a little bash script to simplify all process for all that people who (like me) are always updating with HG. With this script you use always lastest update and it creates a new profile to avoid interferences between any existing profile.
|
|
|
muzzol''
|
|
|
|
|
|
|
|
|
HG_DIR="$HOME/install"
|
|
|
|
|
|
cd "$HG_DIR"
|
|
|
|
|
|
hg clone https://hg.gajim.org/gajim gajim
|
|
|
|
|
|
"$HG_DIR"/gajim/launch.sh -p perfilhg
|
|
|
|
|
|
* In Windows
|
|
|
|
|
|
|
|
|
rem ************ Launching Gajim hg ************
|
|
|
cd src
|
|
|
gajim.py -p hg
|
|
|
|
|
|
save the above as gajim_hg.bat in the Gajim folder (eg. the folder that you have hg). Now you can double click gajim_hg.bat and you can run hg version without mixing with stable one |
|
|
\ No newline at end of file |
|
|
this creates a config.git (eg profile git) and completely separate database and plugins. |