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

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

@ -5,7 +5,8 @@
$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>
@ -20,24 +21,23 @@
xlink:href="http://www.FreshPorts.org/">FreshPorts</link>.
You can select multiple ports to monitor. Maintainers are
strongly encouraged to subscribe, because they will receive
notification of not only their own changes, but also any
changes that any other &os; committer has made. (These are
often necessary to keep up with changes in the underlying
ports framework&mdash;although it would be most polite to
receive an advance heads-up from those committing such
changes, sometimes this is overlooked or just simply
impractical. Also, in some cases, the changes are very minor
in nature. We expect everyone to use their best judgement in
these cases.)</para>
notification of not only their own changes, but also any changes
that any other &os; committer has made. (These are often
necessary to keep up with changes in the underlying ports
framework&mdash;although it would be most polite to receive an
advance heads-up from those committing such changes, sometimes
this is overlooked or just simply impractical. Also, in some
cases, the changes are very minor in nature. We expect everyone
to use their best judgement in these cases.)</para>
<para>If you wish to use FreshPorts, all you need is an account.
If your registered email address is
<literal>@FreeBSD.org</literal>, you will see the opt-in link
on the right hand side of the webpages. For those of you who
<literal>@FreeBSD.org</literal>, you will see the opt-in link on
the right hand side of the webpages. For those of you who
already have a FreshPorts account, but are not using your
<literal>@FreeBSD.org</literal> email address, just change
your email to <literal>@FreeBSD.org</literal>, subscribe, then
change it back again.</para>
<literal>@FreeBSD.org</literal> email address, just change your
email to <literal>@FreeBSD.org</literal>, subscribe, then change
it back again.</para>
<para>FreshPorts also has a sanity test feature which
automatically tests each commit to the &os; ports tree. If
@ -80,15 +80,15 @@
<para>One of the least-publicized strengths of &os; is that
an entire cluster of machines is dedicated to continually
building the Ports Collection, for each of the major OS
releases and for each Tier-1 architecture.</para>
building the Ports Collection, for each of the major OS releases
and for each Tier-1 architecture.</para>
<para>Individual ports are built unless they are specifically
marked with <varname>IGNORE</varname>. Ports that are
marked with <varname>BROKEN</varname> will still be attempted,
to see if the underlying problem has been resolved. (This
is done by passing <varname>TRYBROKEN</varname> to the
port's <filename>Makefile</filename>.)</para>
marked with <varname>IGNORE</varname>. Ports that are marked
with <varname>BROKEN</varname> will still be attempted, to see
if the underlying problem has been resolved. (This is done by
passing <varname>TRYBROKEN</varname> to the port's
<filename>Makefile</filename>.)</para>
</sect1>
<sect1 xml:id="distfile-survey">
@ -112,9 +112,9 @@
the email address of the port maintainer, the number of ports
the maintainer is responsible for, the number of those ports
with new distfiles, and the percentage of those ports that are
out-of-date. The search function allows for searching by
email address for a specific maintainer, and for selecting
whether or not only out-of-date ports should be shown.</para>
out-of-date. The search function allows for searching by email
address for a specific maintainer, and for selecting whether or
not only out-of-date ports should be shown.</para>
<para>Upon clicking on a maintainer's email address, a list of
all of their ports is displayed, along with port category,
@ -131,29 +131,29 @@
<sect1 xml:id="portsmon">
<title>The &os; Ports Monitoring System</title>
<para>Another handy resource is the
<link xlink:href="http://portsmon.FreeBSD.org">&os; Ports
<para>Another handy resource is the <link
xlink:href="http://portsmon.FreeBSD.org">&os; Ports
Monitoring System</link> (also known as
<literal>portsmon</literal>). This system comprises a
database that processes information from several sources and
allows it to be browsed via a web interface. Currently, the
ports Problem Reports (PRs), the error logs from the build
cluster, and individual files from the ports collection are
used. In the future, this will be expanded to include the
distfile survey, as well as other sources.</para>
<literal>portsmon</literal>). This system comprises a database
that processes information from several sources and allows it to
be browsed via a web interface. Currently, the ports Problem
Reports (PRs), the error logs from the build cluster, and
individual files from the ports collection are used. In the
future, this will be expanded to include the distfile survey, as
well as other sources.</para>
<para>To get started, you can view all information about a
particular port by using the <link
xlink:href="http://portsmon.FreeBSD.org/portoverview.py">Overview
of One Port</link>.</para>
<para>As of this writing, this is the only resource available
that maps GNATS PR entries to portnames. (PR submitters do
not always include the portname in their Synopsis, although we
would prefer that they did.) So, <literal>portsmon</literal>
is a good place to start if you want to find out whether an
existing port has any PRs filed against it and/or any build
errors; or, to find out if a new port that you may be thinking
about creating has already been submitted.</para>
<para>As of this writing, this is the only resource available that
maps GNATS PR entries to portnames. (PR submitters do not
always include the portname in their Synopsis, although we would
prefer that they did.) So, <literal>portsmon</literal> is a
good place to start if you want to find out whether an existing
port has any PRs filed against it and/or any build errors; or,
to find out if a new port that you may be thinking about
creating has already been submitted.</para>
</sect1>
</chapter>
</chapter>