mirror of https://gitee.com/openkylin/libvirt.git
125 lines
4.0 KiB
XML
125 lines
4.0 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<body>
|
|
<h1>Downloads</h1>
|
|
|
|
<ul id="toc"></ul>
|
|
|
|
<h2><a name="releases">Official Releases</a></h2>
|
|
|
|
<p>
|
|
The latest versions of the libvirt C library can be downloaded from:
|
|
</p>
|
|
|
|
<ul>
|
|
<li><a href="ftp://libvirt.org/libvirt/">libvirt.org FTP server</a></li>
|
|
<li><a href="http://libvirt.org/sources/">libvirt.org HTTP server</a></li>
|
|
</ul>
|
|
|
|
<h2><a name="hourly">Hourly development snapshots</a></h2>
|
|
|
|
<p>
|
|
Once an hour, an automated snapshot is made from the git server
|
|
source tree. These snapshots should be usable, but we make no guarantees
|
|
about their stability; furthermore, they should NOT be
|
|
considered formal releases, and they may have transient security
|
|
problems that will not be assigned a CVE.
|
|
</p>
|
|
|
|
<ul>
|
|
<li><a href="ftp://libvirt.org/libvirt/libvirt-git-snapshot.tar.gz">libvirt.org FTP server</a></li>
|
|
<li><a href="http://libvirt.org/sources/libvirt-git-snapshot.tar.gz">libvirt.org HTTP server</a></li>
|
|
</ul>
|
|
|
|
<h2><a name="maintenance">Maintenance releases</a></h2>
|
|
<p>
|
|
In the git repository are several stable maintenance branches,
|
|
matching the
|
|
pattern <code>v<i>major</i>.<i>minor</i>.<i>micro</i>-maint</code>;
|
|
these branches are forked off the corresponding
|
|
<code>v<i>major</i>.<i>minor</i>.<i>micro</i></code> formal
|
|
release, and may have further releases of the
|
|
form <code>v<i>major</i>.<i>minor</i>.<i>micro</i>.<i>rel</i></code>.
|
|
These maintenance branches should only contain bug fixes, and no
|
|
new features, backported from the master branch, and are
|
|
supported as long as at least one downstream distribution
|
|
expresses interest in a given branch. These maintenance
|
|
branches are considered during CVE analysis.
|
|
</p>
|
|
|
|
<p>
|
|
For more details about contents of maintenance releases, see
|
|
<a href="http://wiki.libvirt.org/page/Maintenance_Releases">the
|
|
wiki page</a>.
|
|
</p>
|
|
|
|
<h2><a name="git">GIT source repository</a></h2>
|
|
|
|
<p>
|
|
Libvirt code source is now maintained in a <a href="http://git-scm.com/">git</a>
|
|
repository available on <a href="http://libvirt.org/git/">libvirt.org</a>:
|
|
</p>
|
|
|
|
<pre>
|
|
git clone git://libvirt.org/libvirt.git</pre>
|
|
|
|
<p>
|
|
It can also be browsed at:
|
|
</p>
|
|
|
|
<pre>
|
|
<a href="http://libvirt.org/git/?p=libvirt.git;a=summary">http://libvirt.org/git/?p=libvirt.git;a=summary</a></pre>
|
|
|
|
<br />
|
|
|
|
<h1>libvirt Application Development Guide</h1>
|
|
|
|
<p>
|
|
The guide is both a learning tool for developing with libvirt and an
|
|
API reference document. It is a work in progress, composed by a
|
|
professional author from contributions written by members of the
|
|
libvirt team.
|
|
</p>
|
|
|
|
<p>
|
|
Contributions to the guide are <b>VERY</b> welcome. If you'd like to get
|
|
your name on this and demonstrate your virtualisation prowess, a solid
|
|
contribution to the content here will do it. :)
|
|
</p>
|
|
|
|
<h2><a name="appdevpdf">Application Development Guide PDF</a></h2>
|
|
|
|
<p>
|
|
PDF download is available here:
|
|
</p>
|
|
|
|
<ul>
|
|
<li><a href="http://libvirt.org/guide/pdf/Application_Development_Guide.pdf">libvirt App Dev Guide</a> (PDF)</li>
|
|
</ul>
|
|
|
|
<h2><a name="appdevgit">Application Development Guide source GIT repository</a></h2>
|
|
|
|
<p>
|
|
The source is also in a git repository:
|
|
</p>
|
|
|
|
<pre>
|
|
git clone git://libvirt.org/libvirt-appdev-guide.git</pre>
|
|
|
|
<p>
|
|
Browsable at:
|
|
</p>
|
|
|
|
<pre>
|
|
<a href="http://libvirt.org/git/?p=libvirt-appdev-guide.git;a=summary">http://libvirt.org/git/?p=libvirt-appdev-guide.git;a=summary</a></pre>
|
|
|
|
<br />
|
|
|
|
<p>
|
|
Once you've have obtained the libvirt source code, you can compile it
|
|
using the <a href="compiling.html">instructions here</a>.
|
|
</p>
|
|
</body>
|
|
</html>
|