pidgin/nest

bfceef396691
Use hugo refs for resolving links

This will allow us to find broken links easier since if we remove or change
the location of a particular page that's linked in another, then Hugo will
throw a warning/error when this happens if we are using the ref functionality.

The only link that I'm not dealing with here is the one for tips for bug
reports since that page hasn't yet been ported to the new nest site.

Testing Done:
Ran `dev-server.sh` and verified the links that got changed in this PR still worked as intended.

Reviewed at https://reviews.imfreedom.org/r/795/
---
title: Version Control
date: 2019-02-01T05:09:48.000Z
anchor: development
replaces:
- developer.pidgin.im/wiki/UsingPidginMercurial
lastmod: 2019-08-29T20:33:38.000Z
---
All of the source code relating to Pidgin and its libraries is hosted in
[Mercurial](https://www.mercurial-scm.org/) repositories and are specified
below.
### Repositories
Pidgin itself lives in the {{< repo link="1" name="pidgin" >}}, repository.
This include Pidgin 2 on the `release-2.x.y` branch as well as Pidgin 3 on the
`default` branch.
The default branch has moved libgnt out to its own repository at
{{< repo link="1" name="libgnt" >}} to make it more accessible to other
developers. The intent here is to have it be a separate package on all
distributions to make it more accessible to users as well as developers. This
will help on distributions such as Slackware that enforce rules of one
distribution package per source package.
Pidgin 3 also depends on {{< repo link="1" name="talkatu" >}} for reusable
[GTK](https://www.gtk.org) widgets that are geared towards messaging clients.
Purple 3 has adopted {{< repo link="1" name="gplugin" >}}, which is a library
that handles plugins in multiple languages leveraging
[gobject-introspection](https://gi.readthedocs.io/en/latest/). It currently
supports C/C++, Perl, Python, and Lua plugins, with more languages planned for
the future.