aboutsummaryrefslogtreecommitdiff
path: root/doc/index.html.skel
blob: 74cc14532e17c11eb6bcd280927c4cd3e04c4697 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xml:lang="en">
<head>
<title>Paludis, the Other Package Mangler</title>
<link rel="stylesheet" href="paludis.css" type="text/css" />
</head>
<body>
@HEADER@

    <h1>Paludis, the Other Package Mangler</h1>

    <p>Paludis is a package manager for use with <a
        href="http://www.gentoo.org/">Gentoo</a> and related distributions. It
    is entirely independent of Portage. The current version is <strong>@VERSION@</strong>,
    with the following changes:</p>

@RECENTNEWS@

    <p>See the <a href="news.html">Release Notes</a> for previous releases.</p>

    <h2>For prospective users:</h2>

    <ul>
        <li>An overview of <a href="portagedifferences.html">the differences between
            Paludis and its predecessor, Portage</a>.</li>

        <li>A <a href="migration.html">guide to migrating to
            Paludis</a>.</li>
    </ul>

    <h2>For current users:</h2>

    <ul>
        <li>An <a href="faq.html">FAQ</a> is available. You should familiarise
        yourself with this list before asking questions.</li>

        <li>The <a href="news.html">release notes</a> document major
        changes between releases. More detailed information is available
        in the <a href="changelog.html">changelog</a>.</li>

        <li>There is <a href="configuration.html">documentation on the
            configuration files</a> and <a href="cachefiles.html">the
            various optional caches</a> used by Paludis. There is also documentation on
        <a href="sets.html">sets (including how user defined sets work)</a> and
        <a href="hooks.html">hooks (and how user defined hooks work)</a>.</li>

        <li><strong>Support</strong> is available via <code>#paludis</code> on
        <code>irc.freenode.net</code> or the <a
            href="http://lists.pioto.org/">mailing
            lists</a>.  There is a <a
            href="http://paludis.pioto.org/trac/">bug tracker</a> that can
        be used for bug reports and feature requests.</li>

        <li>Manual pages:
        <ul>
            <li><a href="man-adjutrix.html">adjutrix</a></li>
            <li><a href="man-contrarius.html">contrarius</a></li>
            <li><a href="man-inquisitio.html">inquisitio</a></li>
            <li><a href="man-paludis.html">paludis</a></li>
            <li><a href="man-qualudis.html">qualudis</a></li>
        </ul>
        </li>

    </ul>

    <h2>For developers:</h2>

    <ul>
        <li><strong>Subversion access</strong> is available via
        <code>svn co svn://svn.pioto.org/paludis/trunk paludis</code>. There
        is also <a href="http://paludis.pioto.org/trac/browser">Trac's
            code browser</a> for viewing via the web.</li>

        <li>An <a href="programmingwithpaludis.html">overview of
            Programming with Paludis</a>, covering both the C++ and the
        Ruby APIs, is available.</li>

        <li>There is <a href="doxygen/html"/>extensive C++ core API and implementation
            documentation</a>. This is also available via <code>make
            doxygen</code>.</li>

        <li>Similarly, the <a href="ruby/">Ruby API documentation</a> is available
        via <code>make rdoc</code> and the <a href="python/doc/">Python API documentation</a>
        via <code>make epydoc</code>.</li>

        <li><strong>Development questions</strong> should be asked in <code>#paludis</code> on
        <code>irc.freenode.net</code> or on the <a
            href="http://lists.pioto.org/">mailing lists</a>.
        Patches go to the <a href="http://paludis.pioto.org/trac/">bug tracker</a>.</li>

    </ul>

@FOOTER@
</body>
</html>