Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
howtos:testing_git [2017/04/30 14:47] – created vfaronovhowtos:testing_git [2017/07/09 01:15] (current) – how to find the versions of GTK+ and GLib used vfaronov
Line 1: Line 1:
-==== Trying out development versions of Geany ====+====== Trying out development versions of Geany ======
  
 **Testing** is a useful way to contribute to Geany. **Testing** is a useful way to contribute to Geany.
Line 5: Line 5:
 If you're running Linux, it's easy and safe to try out a development version of Geany without affecting your existing Geany setup. This tutorial will show you how. It assumes that you are more or less familiar with the Unix shell. Familiarity with [[https://git-scm.com/|Git]] will help but is not required. If you're running Linux, it's easy and safe to try out a development version of Geany without affecting your existing Geany setup. This tutorial will show you how. It assumes that you are more or less familiar with the Unix shell. Familiarity with [[https://git-scm.com/|Git]] will help but is not required.
  
-=== Getting started ===+===== Getting started =====
  
-To begin, you will need the GNU toolchain, Git, and GTK+. You can install them with your system's package manager. This should work for Ubuntu or Debian:+To begin, you will need the GNU toolchain, Git, and the GTK+ and VTE libraries. You can install them with your system's package manager. This should work for Ubuntu or Debian:
  
 <code> <code>
-$ sudo apt install build-essential git libgtk2.0-dev+$ sudo apt install build-essential autoconf automake libtool intltool git libgtk2.0-dev libvte-dev
 </code> </code>
  
 **TODO: equivalents for Fedora etc.** **TODO: equivalents for Fedora etc.**
 +
 +If you've never used Git before, you may need to set it up with your name and email (the values you enter don't matter for this tutorial):
 +
 +<code>
 +$ git config --global user.name "Your Name"
 +$ git config --global user.email your.email@example.com
 +</code>
  
 It may be convenient to create a dedicated directory for testing Geany. This tutorial will use ''~/geany'': It may be convenient to create a dedicated directory for testing Geany. This tutorial will use ''~/geany'':
Line 52: Line 59:
 </code> </code>
  
-=== Using your real configuration ===+===== Using your real configuration =====
  
 The ''-c'' option above told Geany to keep all its config in the ''~/geany/config1'' directory. Without a ''-c'' option, Geany uses a default location -- normally ''~/.config/geany''. So, if you have a regular, system-wide installation of Geany, its config is safe and completely independent from the development version. The ''-c'' option above told Geany to keep all its config in the ''~/geany/config1'' directory. Without a ''-c'' option, Geany uses a default location -- normally ''~/.config/geany''. So, if you have a regular, system-wide installation of Geany, its config is safe and completely independent from the development version.
Line 65: Line 72:
 In fact, you can create as many config directories as you like, and run an independent instance of Geany for each of them. In fact, you can create as many config directories as you like, and run an independent instance of Geany for each of them.
  
-=== How to test ===+===== How to test =====
  
 Check some of your favorite features of Geany -- do they work as expected? Check some of your favorite features of Geany -- do they work as expected?
Line 71: Line 78:
 Try working as you would normally. Open a project, try editing code in a meaningful way. Try working as you would normally. Open a project, try editing code in a meaningful way.
  
-If you discover problems, [[https://github.com/geany/geany/issues/new|submit an issue on GitHub]]. Include the Git revision you're running -- you can see it in Geany's "About" box (//Help// → //About//): ''git >= 0d47e09''+If you discover problems, [[https://github.com/geany/geany/issues/new|submit an issue on GitHub]]. Include the Git revision you're running -- you can see it in Geany's "About" box (//Help// → //About//): ''git >= 0d47e09''. Your versions of GTK+ and GLib may also be important -- you can find them in the first lines of //Help// → //Debug Messages//.
  
-=== Testing a pull request ===+===== Testing a pull request =====
  
 Geany is developed [[https://github.com/geany/geany|on GitHub]], and people propose changes or additions to Geany in the form of [[https://github.com/geany/geany/pulls|pull requests]] (PRs). Sometimes there is a PR that looks good, but needs more testing in various scenarios. This is where you can help. Geany is developed [[https://github.com/geany/geany|on GitHub]], and people propose changes or additions to Geany in the form of [[https://github.com/geany/geany/pulls|pull requests]] (PRs). Sometimes there is a PR that looks good, but needs more testing in various scenarios. This is where you can help.
Line 132: Line 139:
 </code> </code>
  
-=== Running on a regular basis ===+===== Plugins ===== 
 + 
 +**TODO: how to install Geany-Plugins from Git as well** 
 + 
 +===== Running on a regular basis =====
  
 It's very useful to try out a development version for 10 minutes. But it's even more useful to run a development version for 2 weeks as your main instance of Geany, if you're comfortable with that. Some problems can only be discovered when you're doing regular work. It's very useful to try out a development version for 10 minutes. But it's even more useful to run a development version for 2 weeks as your main instance of Geany, if you're comfortable with that. Some problems can only be discovered when you're doing regular work.
  
 **TODO: installing into /usr/local, etc.** **TODO: installing into /usr/local, etc.**

Trace:

Print/export