Not the release engineering team is responsible for
creating high quality packages but the ports management
team.
PR: www/94099 (inspired by).
Submitted by: Kovesdan Gabor <gabor dot kovesdan at t-hosting dot hu>
Verified by: scotll
Currently we have articles.ent and books.ent, and
for example, articles.ent can be used by putting the
following lines in the doctype declaration:
<!ENTITY % articles.ent PUBLIC
"-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
%articles.ent;
This pulls all of the necessary entities via share/sgml/articles.ent.
The translation teams can customize these entities by redefining
the articles.ent file in <langcode>/share/sgml. See
ja_JP.eucJP/share/sgml for example.
- Add trademark attributions.
- Don't join trademarks with other words, e.g. using hyphens.
- Don't use trademarks as nouns (e.g. don't use "Windows NT's").
enable it in en_US.ISO8859-1/ and ja_JP.eucJP/.
- Add PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN"
and l10n.ent for entity localization.
- Use share/misc/docbook.css for indentiation of <programlisting>
and <screen>.
- Add some missing $FreeBSD$.
time). Point users to the right location in the ports tree. Also
adjust certain pathname references to reflect reality.
Inspired by: talk(1) session with will
third party software packages that accompany an official FreeBSD
release.
This document currently describes the "package split" procedure that
Steve Price uses to create clusters of like packages with similar
dependencies that are grouped onto specific discs.
In the future, this article should document the scripts that generate
clean packages on the bento cluster, the steps necessary to setup
another group of machines as a "Ports Cluster", and the scripts that
are used to verify the integrity of a package split.
Submitted by: steve
Sponsored by: FreeBSD Mall, Inc.
