os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Whitespace-only fixes, translators please ignore.

Browse source
This commit is contained in:
Warren Block 2014-02-09 03:04:10 +00:00
parent edfa4e2c28
commit 5389e307fe
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=43846
1 changed files with 128 additions and 128 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

256
en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml
View file

@ -5,155 +5,155 @@
$FreeBSD$ $FreeBSD$
--> -->
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="keeping-up"> <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink=
"http://www.w3.org/1999/xlink" version="5.0" xml:id="keeping-up">
<title>Keeping Up</title> <title>Keeping Up</title>
<para>The &os; Ports Collection is constantly changing. Here is <para>The &os; Ports Collection is constantly changing. Here is
some information on how to keep up.</para> some information on how to keep up.</para>
<sect1 xml:id="freshports"> <sect1 xml:id="freshports">
<title>FreshPorts</title> <title>FreshPorts</title>
<para>One of the easiest ways to learn about updates that have <para>One of the easiest ways to learn about updates that have
already been committed is by subscribing to <link already been committed is by subscribing to <link
xlink:href="http://www.FreshPorts.org/">FreshPorts</link>. xlink:href="http://www.FreshPorts.org/">FreshPorts</link>.
You can select multiple ports to monitor. Maintainers are You can select multiple ports to monitor. Maintainers are
strongly encouraged to subscribe, because they will receive strongly encouraged to subscribe, because they will receive
notification of not only their own changes, but also any notification of not only their own changes, but also any changes
changes that any other &os; committer has made. (These are that any other &os; committer has made. (These are often
often necessary to keep up with changes in the underlying necessary to keep up with changes in the underlying ports
ports framework&mdash;although it would be most polite to framework&mdash;although it would be most polite to receive an
receive an advance heads-up from those committing such advance heads-up from those committing such changes, sometimes
changes, sometimes this is overlooked or just simply this is overlooked or just simply impractical. Also, in some
impractical. Also, in some cases, the changes are very minor cases, the changes are very minor in nature. We expect everyone
in nature. We expect everyone to use their best judgement in to use their best judgement in these cases.)</para>
these cases.)</para>
<para>If you wish to use FreshPorts, all you need is an account. <para>If you wish to use FreshPorts, all you need is an account.
If your registered email address is If your registered email address is
<literal>@FreeBSD.org</literal>, you will see the opt-in link <literal>@FreeBSD.org</literal>, you will see the opt-in link on
on the right hand side of the webpages. For those of you who the right hand side of the webpages. For those of you who
already have a FreshPorts account, but are not using your already have a FreshPorts account, but are not using your
<literal>@FreeBSD.org</literal> email address, just change <literal>@FreeBSD.org</literal> email address, just change your
your email to <literal>@FreeBSD.org</literal>, subscribe, then email to <literal>@FreeBSD.org</literal>, subscribe, then change
change it back again.</para> it back again.</para>
<para>FreshPorts also has a sanity test feature which <para>FreshPorts also has a sanity test feature which
automatically tests each commit to the &os; ports tree. If automatically tests each commit to the &os; ports tree. If
subscribed to this service, you will be notified of any errors subscribed to this service, you will be notified of any errors
which FreshPorts detects during sanity testing of your which FreshPorts detects during sanity testing of your
commits.</para> commits.</para>
</sect1> </sect1>
<sect1 xml:id="svnweb"> <sect1 xml:id="svnweb">
<title>The Web Interface to the Source Repository</title> <title>The Web Interface to the Source Repository</title>
<para>It is possible to browse the files in the source <para>It is possible to browse the files in the source
repository by using a web interface. Changes that affect the repository by using a web interface. Changes that affect the
entire port system are now documented in the <link entire port system are now documented in the <link
xlink:href="http://svnweb.FreeBSD.org/ports/head/CHANGES">CHANGES</link> xlink:href="http://svnweb.FreeBSD.org/ports/head/CHANGES">CHANGES</link>
file. Changes that affect individual ports are now documented file. Changes that affect individual ports are now documented
in the <link in the <link
xlink:href="http://svnweb.FreeBSD.org/ports/head/UPDATING">UPDATING</link> xlink:href="http://svnweb.FreeBSD.org/ports/head/UPDATING">UPDATING</link>
file. However, the definitive answer to any question is file. However, the definitive answer to any question is
undoubtedly to read the source code of <link undoubtedly to read the source code of <link
xlink:href="http://svnweb.FreeBSD.org/ports/head/Mk/bsd.port.mk">bsd.port.mk</link>, xlink:href="http://svnweb.FreeBSD.org/ports/head/Mk/bsd.port.mk">bsd.port.mk</link>,
and associated files.</para> and associated files.</para>
</sect1> </sect1>
<sect1 xml:id="ports-mailing-list"> <sect1 xml:id="ports-mailing-list">
<title>The &os; Ports Mailing List</title> <title>The &os; Ports Mailing List</title>
<para>If you maintain ports, you should consider following the <para>If you maintain ports, you should consider following the
&a.ports;. Important changes to the way ports work will be &a.ports;. Important changes to the way ports work will be
announced there, and then committed to announced there, and then committed to
<filename>CHANGES</filename>.</para> <filename>CHANGES</filename>.</para>
<para>If this mailing list is too high volume you may consider <para>If this mailing list is too high volume you may consider
following &a.ports-announce; which is moderated and has no following &a.ports-announce; which is moderated and has no
discussion.</para> discussion.</para>
</sect1> </sect1>
<sect1 xml:id="build-cluster"> <sect1 xml:id="build-cluster">
<title>The &os; Port Building Cluster</title> <title>The &os; Port Building Cluster</title>
<para>One of the least-publicized strengths of &os; is that <para>One of the least-publicized strengths of &os; is that
an entire cluster of machines is dedicated to continually an entire cluster of machines is dedicated to continually
building the Ports Collection, for each of the major OS building the Ports Collection, for each of the major OS releases
releases and for each Tier-1 architecture.</para> and for each Tier-1 architecture.</para>
<para>Individual ports are built unless they are specifically <para>Individual ports are built unless they are specifically
marked with <varname>IGNORE</varname>. Ports that are marked with <varname>IGNORE</varname>. Ports that are marked
marked with <varname>BROKEN</varname> will still be attempted, with <varname>BROKEN</varname> will still be attempted, to see
to see if the underlying problem has been resolved. (This if the underlying problem has been resolved. (This is done by
is done by passing <varname>TRYBROKEN</varname> to the passing <varname>TRYBROKEN</varname> to the port's
port's <filename>Makefile</filename>.)</para> <filename>Makefile</filename>.)</para>
</sect1> </sect1>
<sect1 xml:id="distfile-survey"> <sect1 xml:id="distfile-survey">
<title>Portscout: the &os; Ports Distfile Scanner</title> <title>Portscout: the &os; Ports Distfile Scanner</title>
<para>The build cluster is dedicated to building the latest <para>The build cluster is dedicated to building the latest
release of each port with distfiles that have already been release of each port with distfiles that have already been
fetched. However, as the Internet continually changes, fetched. However, as the Internet continually changes,
distfiles can quickly go missing. <link distfiles can quickly go missing. <link
xlink:href="http://portscout.FreeBSD.org">Portscout</link>, xlink:href="http://portscout.FreeBSD.org">Portscout</link>,
the &os; Ports distfile scanner, attempts to query every the &os; Ports distfile scanner, attempts to query every
download site for every port to find out if each distfile is download site for every port to find out if each distfile is
still available. <application>Portscout</application> can still available. <application>Portscout</application> can
generate <acronym>HTML</acronym> reports and send emails about generate <acronym>HTML</acronym> reports and send emails about
newly available ports to those who request them. Unless not newly available ports to those who request them. Unless not
otherwise subscribed, maintainers are asked to check otherwise subscribed, maintainers are asked to check
periodically for changes, either by hand or using the periodically for changes, either by hand or using the
<acronym>RSS</acronym> feed.</para> <acronym>RSS</acronym> feed.</para>
<para><application>Portscout</application>'s first page gives <para><application>Portscout</application>'s first page gives
the email address of the port maintainer, the number of ports the email address of the port maintainer, the number of ports
the maintainer is responsible for, the number of those ports the maintainer is responsible for, the number of those ports
with new distfiles, and the percentage of those ports that are with new distfiles, and the percentage of those ports that are
out-of-date. The search function allows for searching by out-of-date. The search function allows for searching by email
email address for a specific maintainer, and for selecting address for a specific maintainer, and for selecting whether or
whether or not only out-of-date ports should be shown.</para> not only out-of-date ports should be shown.</para>
<para>Upon clicking on a maintainer's email address, a list of <para>Upon clicking on a maintainer's email address, a list of
all of their ports is displayed, along with port category, all of their ports is displayed, along with port category,
current version number, whether or not there is a new version, current version number, whether or not there is a new version,
when the port was last updated, and finally when it was last when the port was last updated, and finally when it was last
checked. A search function on this page allows the user to checked. A search function on this page allows the user to
search for a specific port.</para> search for a specific port.</para>
<para>Clicking on a port name in the list displays the <link <para>Clicking on a port name in the list displays the <link
xlink:href="http://freshports.org">FreshPorts</link> port xlink:href="http://freshports.org">FreshPorts</link> port
information.</para> information.</para>
</sect1> </sect1>
<sect1 xml:id="portsmon"> <sect1 xml:id="portsmon">
<title>The &os; Ports Monitoring System</title> <title>The &os; Ports Monitoring System</title>
<para>Another handy resource is the <para>Another handy resource is the <link
<link xlink:href="http://portsmon.FreeBSD.org">&os; Ports xlink:href="http://portsmon.FreeBSD.org">&os; Ports
Monitoring System</link> (also known as Monitoring System</link> (also known as
<literal>portsmon</literal>). This system comprises a <literal>portsmon</literal>). This system comprises a database
database that processes information from several sources and that processes information from several sources and allows it to
allows it to be browsed via a web interface. Currently, the be browsed via a web interface. Currently, the ports Problem
ports Problem Reports (PRs), the error logs from the build Reports (PRs), the error logs from the build cluster, and
cluster, and individual files from the ports collection are individual files from the ports collection are used. In the
used. In the future, this will be expanded to include the future, this will be expanded to include the distfile survey, as
distfile survey, as well as other sources.</para> well as other sources.</para>
<para>To get started, you can view all information about a <para>To get started, you can view all information about a
particular port by using the <link particular port by using the <link
xlink:href="http://portsmon.FreeBSD.org/portoverview.py">Overview xlink:href="http://portsmon.FreeBSD.org/portoverview.py">Overview
of One Port</link>.</para> of One Port</link>.</para>
<para>As of this writing, this is the only resource available <para>As of this writing, this is the only resource available that
that maps GNATS PR entries to portnames. (PR submitters do maps GNATS PR entries to portnames. (PR submitters do not
not always include the portname in their Synopsis, although we always include the portname in their Synopsis, although we would
would prefer that they did.) So, <literal>portsmon</literal> prefer that they did.) So, <literal>portsmon</literal> is a
is a good place to start if you want to find out whether an good place to start if you want to find out whether an existing
existing port has any PRs filed against it and/or any build port has any PRs filed against it and/or any build errors; or,
errors; or, to find out if a new port that you may be thinking to find out if a new port that you may be thinking about
about creating has already been submitted.</para> creating has already been submitted.</para>
</sect1> </sect1>
</chapter> </chapter>