glfs/general/prog/py3c.xml
Bruce Dubbs 03a2986c05 A package update and some tags.
Update to libqalculate-4.0.0.
2022-02-16 22:44:55 -06:00

136 lines
3.5 KiB
XML

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../../general.ent">
%general-entities;
<!ENTITY py3c-download-http
"https://github.com/encukou/py3c/archive/v&py3c-version;/py3c-&py3c-version;.tar.gz">
<!ENTITY py3c-md5sum "53029afde7e0cf8672a2d69d378a0cfc">
<!ENTITY py3c-size "47 KB">
<!ENTITY py3c-buildsize "608 KB">
<!ENTITY py3c-time "less than 0.1 SBU">
]>
<!-- Begin Py3c -->
<sect2 id="py3c" xreflabel="Py3c-&py3c-version;">
<title>Py3c-&py3c-version;</title>
<indexterm zone="py3c">
<primary sortas="a-Py3c">Py3c</primary>
</indexterm>
<sect3 role="package">
<title>Introduction to Py3c</title>
<para>
<application>Py3c</application> helps you port C extensions to
Python 3. It provides a detailed guide, and a set of macros to
make porting easy and reduce boilerplate.
</para>
&lfs111_checked;
<bridgehead renderas="sect4">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>
Download (HTTP): <ulink url="&py3c-download-http;"/>
</para>
</listitem>
<!--
<listitem>
<para>
Download (FTP): <ulink url="&py3c-download-ftp;"/>
</para>
</listitem>
-->
<listitem>
<para>
Download MD5 sum: &py3c-md5sum;
</para>
</listitem>
<listitem>
<para>
Download size: &py3c-size;
</para>
</listitem>
<listitem>
<para>
Estimated disk space required: &py3c-buildsize;
</para>
</listitem>
<listitem>
<para>
Estimated build time: &py3c-time;
</para>
</listitem>
</itemizedlist>
<!--
<bridgehead renderas="sect4">Py3c Dependencies</bridgehead>
<bridgehead renderas="sect5">Required</bridgehead>
<para role="required">
-->
<para condition="html" role="usernotes">
User Notes: <ulink url="&blfs-wiki;/py3c"/>
</para>
</sect3>
<sect3 role="installation">
<title>Installation of Py3c</title>
<para>
The <application>Py3c</application> package is a headers-only package
and because of that, no configuration and compilation is
required.
</para>
<para>
To test the package, issue:
</para>
<screen remap="test"><userinput>make test-python3 &amp;&amp;
make test-python3-cpp</userinput></screen>
<para>
To install the <application>Python 3</application> module,
run the following command as the
<systemitem class="username">root</systemitem> user:
</para>
<!-- Note:
Now, doing a DESTDIR install is just
"make prefix=/usr DESTDIR=<dest> install"
-->
<screen role="root"><userinput>make prefix=/usr install</userinput></screen>
</sect3>
<sect3 role="content">
<title>Contents</title>
<segmentedlist>
<segtitle>Installed Programs</segtitle>
<segtitle>Installed Libraries</segtitle>
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>
None
</seg>
<seg>
None
</seg>
<seg>
/usr/include/py3c
</seg>
</seglistitem>
</segmentedlist>
</sect3>
</sect2>