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

Add missing tags for x11 category, use same tags type in all

Browse source 
categories section, and few fixes.
This commit is contained in:
Marc Fonvieille 2002-08-13 10:13:46 +00:00
parent fc39074987
commit 5320eb6c49
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13845
1 changed files with 15 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -1603,8 +1603,8 @@ PORTEPOCH= 1</programlisting>
</row> </row>
<row> <row>
<entry>x11</entry> <entry><filename>x11</filename></entry>
<entry>The X window system and friends. This category is only <entry>The X Window System and friends. This category is only
for software that directly supports the window system. Do not for software that directly supports the window system. Do not
put regular X applications here. If your port is an X put regular X applications here. If your port is an X
application, define <makevar>USE_XLIB</makevar> (implied by application, define <makevar>USE_XLIB</makevar> (implied by
@ -1658,30 +1658,30 @@ PORTEPOCH= 1</programlisting>
<para>As many of the categories overlap, you often have to choose <para>As many of the categories overlap, you often have to choose
which of the categories should be the primary category of your port. which of the categories should be the primary category of your port.
There are several rules that govern this issue. Here is the list of There are several rules that govern this issue. Here is the list of
priorities, in decreasing order of precedence.</para> priorities, in decreasing order of precedence:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>Language specific categories always come first. For <para>Language specific categories always come first. For
example, if your port installs Japanese X11 fonts, then your example, if your port installs Japanese X11 fonts, then your
<makevar>CATEGORIES</makevar> line would read <literal>japanese <makevar>CATEGORIES</makevar> line would read <filename>japanese
x11-fonts</literal>.</para> x11-fonts</filename>.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Specific categories win over less-specific ones. For <para>Specific categories win over less-specific ones. For
instance, an HTML editor should be listed as <literal>www instance, an HTML editor should be listed as <filename>www
editors</literal>, not the other way around. Also, you do not editors</filename>, not the other way around. Also, you do not
need to list <literal>net</literal> when the port belongs to need to list <filename>net</filename> when the port belongs to
any of <literal>irc</literal>, <literal>mail</literal>, any of <filename>irc</filename>, <filename>mail</filename>,
<literal>mbone</literal>, <literal>news</literal>, <filename>mbone</filename>, <filename>news</filename>,
<literal>security</literal>, or <literal>www</literal>.</para> <filename>security</filename>, or <filename>www</filename>.</para>
</listitem> </listitem>
<listitem> <listitem>
<para><literal>x11</literal> is used as a secondary category only <para><filename>x11</filename> is used as a secondary category only
when the primary category is a natural language. In particular, when the primary category is a natural language. In particular,
you should not put <literal>x11</literal> in the category line you should not put <filename>x11</filename> in the category line
for X applications.</para> for X applications.</para>
</listitem> </listitem>
@ -1698,12 +1698,12 @@ PORTEPOCH= 1</programlisting>
<listitem> <listitem>
<para>If your port truly does not belong anywhere else, put it in <para>If your port truly does not belong anywhere else, put it in
<literal>misc</literal>.</para> <filename>misc</filename>.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>If you are not sure about the category, please put a comment to <para>If you are not sure about the category, please put a comment to
that effect in your <command>send-pr</command> submission so we can that effect in your &man.send-pr.1; submission so we can
discuss it before we import it. If you are a committer, send a note discuss it before we import it. If you are a committer, send a note
to the &a.ports; so we can discuss it first&mdash;too often new ports are to the &a.ports; so we can discuss it first&mdash;too often new ports are
imported to the wrong category only to be moved right away.</para> imported to the wrong category only to be moved right away.</para>