Source string Read only

(itstool) path: sect2/para
344/3440
Context English State
Tier 2 platforms should provide functional kernels and userlands even if an official release distribution is not provided.
To maintain maturity of Tier 2 platforms, the FreeBSD Project will maintain the following resources to support development:
Collectively, developers are required to provide the following to maintain the Tier 2 status of a platform:
Changes to the source tree should not knowingly break the build of a Tier 2 platform.
Tier 2 architectures must have an active ecosystem of users and developers.
While changes are permitted to break the userland ABI, the ABI should not be broken gratuitously. Significant userland ABI changes should be restricted to major versions.
New features that are not yet implemented on Tier 2 architectures should provide a means of disabling them on those architectures.
Tier 3: Experimental Architectures
Tier 3 platforms have at least partial FreeBSD support. They are <emphasis>not</emphasis> supported by the security officer, release engineering, and port management teams.
Tier 3 platforms are architectures in the early stages of development, for non-mainstream hardware platforms, or which are considered legacy systems unlikely to see broad future use. Initial support for Tier 3 platforms may exist in a separate repository rather than the main source repository.
The FreeBSD Project provides no guarantees to consumers of Tier 3 platforms and is not committed to maintaining resources to support development. Tier 3 platforms may not always be buildable, nor are any kernel or userland ABIs considered stable.
Tier 4: Unsupported Architectures
Tier 4 platforms are not supported in any form by the project.
All systems not otherwise classified are Tier 4 systems. When a platform transitions to Tier 4, all support for the platform is removed from the source and ports trees. Note that ports support should remain as long as the platform is supported in a branch supported by ports.
Policy on Changing the Tier of an Architecture
Systems may only be moved from one tier to another by approval of the FreeBSD Core Team, which shall make that decision in collaboration with the Security Officer, Release Engineering, and ports management teams. For a platform to be promoted to a higher tier, any missing support guarantees must be satisfied before the promotion is completed.
Ports Specific FAQ
Adding a New Port
How do I add a new port?
First, please read the section about repository copies.
The easiest way to add a new port is the <command>addport</command> script located in the <filename>ports/Tools/scripts</filename> directory. It adds a port from the directory specified, determining the category automatically from the port <filename>Makefile</filename>. It also adds an entry to the port's category <filename>Makefile</filename>. It was written by Michael Haro <email>mharo@FreeBSD.org</email>, Will Andrews <email>will@FreeBSD.org</email>, and Renato Botelho <email>garga@FreeBSD.org</email>. When sending questions about this script to the <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports">FreeBSD ports mailing list</link>, please also CC Chris Rees <email>crees@FreeBSD.org</email>, the current maintainer.
Any other things I need to know when I add a new port?
Check the port, preferably to make sure it compiles and packages correctly. This is the recommended sequence:
<prompt>#</prompt> <userinput>make install</userinput>
<prompt>#</prompt> <userinput>make package</userinput>
<prompt>#</prompt> <userinput>make deinstall</userinput>
<prompt>#</prompt> <userinput>pkg add <replaceable>package you built above</replaceable></userinput>
<prompt>#</prompt> <userinput>make deinstall</userinput>
<prompt>#</prompt> <userinput>make reinstall</userinput>
<prompt>#</prompt> <userinput>make package</userinput>
The <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/porters-handbook/index.html">Porters Handbook</link> contains more detailed instructions.
Use <citerefentry vendor="ports"><refentrytitle>portlint</refentrytitle><manvolnum>1</manvolnum></citerefentry> to check the syntax of the port. You do not necessarily have to eliminate all warnings but make sure you have fixed the simple ones.
If the port came from a submitter who has not contributed to the Project before, add that person's name to the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributors/contrib-additional.html">Additional Contributors</link> section of the FreeBSD Contributors List.
Close the PR if the port came in as a PR. To close a PR, change the state to <literal>Issue Resolved</literal> and the resolution as <literal>Fixed</literal>.
Removing an Existing Port
How do I remove an existing port?
First, please read the section about repository copies. Before you remove the port, you have to verify there are no other ports depending on it.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/para
Flags
read-only
Source string location
article.translate.xml:4282
String age
a year ago
Source string age
a year ago
Translation file
articles/committers-guide.pot, string 782