Changeset View
Changeset View
Standalone View
Standalone View
en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml
Show First 20 Lines • Show All 404 Lines • ▼ Show 20 Lines | Packages</quote>, component <quote>Individual Port(s)</quote>, | ||||
Add a short description of the program to the Description field | Add a short description of the program to the Description field | ||||
of the PR (perhaps a short version of | of the PR (perhaps a short version of | ||||
<varname>COMMENT</varname>), and remember to add | <varname>COMMENT</varname>), and remember to add | ||||
<filename>oneko.shar</filename> or | <filename>oneko.shar</filename> or | ||||
<filename>oneko.diff</filename> as an attachment.</para> | <filename>oneko.diff</filename> as an attachment.</para> | ||||
<note> | <note> | ||||
<para>Giving a good description in the summary of the problem | <para>Giving a good description in the summary of the problem | ||||
report makes the work of port committers a lot easier. We | report makes the work of port committers and triagers a lot easier. | ||||
prefer something like <quote>New port: | The expected format for new ports is <quote>[NEW PORT] | ||||
<replaceable>category</replaceable>/<replaceable>portname</replaceable> | <replaceable>category</replaceable>/<replaceable>portname</replaceable>: | ||||
<replaceable>short description of | <replaceable>short description of | ||||
the port</replaceable></quote> for new ports. Using this | the port</replaceable></quote> for new ports. To describe | ||||
the port, the content of <varname>COMMENT</varname> can be | |||||
used. Using this | |||||
crees: We report? | |||||
scheme makes it easier and faster to begin the work of | scheme makes it easier and faster to begin the work of | ||||
committing the new port.</para> | committing the new port.</para> | ||||
</note> | </note> | ||||
Done Inline Actions"short description of the port" was just right, why complicate it with some obscure variable expansion. mat: "short description of the port" was just right, why complicate it with some obscure variable… | |||||
Done Inline ActionsOh, do you mean the content of the COMMENT variable in the port? If so, it would be preferrable to leave the "short description of the port" so that it is easy to understand, and maybe add a note saying something like: To describe the port, the content of the <varname>COMMENT</varname> variable can be used. mat: Oh, do you mean the content of the `COMMENT` variable in the port?
If so, it would be… | |||||
Done Inline ActionsWhat is this <span class="quote">? mat: What is this `<span class="quote">`? | |||||
<para>After submitting the port, please be patient. The time | <para>After submitting the port, please be patient. The time | ||||
needed to include a new port in &os; can vary from a few days | needed to include a new port in &os; can vary from a few days | ||||
to a few months. A simple search form of the Problem Report | to a few months. A simple search form of the Problem Report | ||||
database can be searched at <link | database can be searched at <link | ||||
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi"></link>.</para> | xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi"></link>.</para> | ||||
<para>To get a listing of <emphasis>open</emphasis> port | <para>To get a listing of <emphasis>open</emphasis> port | ||||
<acronym>PR</acronym>s, select <emphasis>Open</emphasis> and | <acronym>PR</acronym>s, select <emphasis>Open</emphasis> and | ||||
Show All 10 Lines |
We report?