cfd9e12239
- Move includes.nav*.sgml to share/sgml/navibar.ent and
<lang>/share/sgml/nabibar.l10n.ent.
- Move includes.sgml and includes.xsl to
share/sgml/common.ent, share/sgml/header.ent, <lang>/share/sgml/l10n.ent,
and <lang>?share/sgml/header.l10n.ent.
- Move most of XSLT libraries to share/sgml/*.xsl and
<lang>/share/sgml/*.xsl.
- Move news.xml and other *.xml files for the similar purpose
to share/sgml/*.xml and <lang>/share/sgml/*.xml.
- Switch to use a custom DTD for HTML document. Now we use
"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension", which is
HTML 4.01 + some entities previously pulled via
"<!ENTITY % includes SYSTEM "includes.sgml"> %includes;" line.
The location of entity file will be resolved by using catalog file.
- Add DOCTYPE declearation to XML documents. This makes the followings
possible:
* Use of &foo; entities for SGML in an XML file instead of defining
{$foo} as the same content.
* &symbolic; entities for Latin characters.
- Duplicated information between SGML and XML, or English and
translated doc, has been removed as much as possible.
69 lines
2.9 KiB
Text
69 lines
2.9 KiB
Text
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
|
|
<!ENTITY base CDATA '..'>
|
|
<!ENTITY date "$FreeBSD: www/en/ports/index.sgml,v 1.2 2006/01/21 12:52:25 pav Exp $">
|
|
<!ENTITY title 'About FreeBSD Ports'>
|
|
<!ENTITY % navinclude.ports "INCLUDE">
|
|
<!ENTITY % ports.ent SYSTEM "ports.ent">
|
|
%ports.ent;
|
|
<!ENTITY email 'ports'>
|
|
%statistics.ent;
|
|
]>
|
|
<HTML>&header;
|
|
|
|
&searchform;
|
|
|
|
<HR>
|
|
|
|
<P>The FreeBSD Ports and Packages Collection offers a simple way for
|
|
users and administrators to install applications. There are currently
|
|
<A HREF="growth/status.png"><B>&ports.count;</B></A> ports available.
|
|
</P>
|
|
|
|
<P>The Ports Collection supports the latest release on the
|
|
<A HREF="&base;/doc/en_US.ISO8859-1/books/faq/introduction.html#CURRENT">
|
|
FreeBSD-CURRENT</A> and
|
|
<A HREF="&base;/doc/en_US.ISO8859-1/books/faq/introduction.html#STABLE">
|
|
FreeBSD-STABLE</A> branches. Older releases are not
|
|
supported and may or may not work correctly with an up-to-date ports
|
|
collection. Over time, changes to the ports collection may rely on
|
|
features that are not present in older releases. Wherever convenient,
|
|
we try not to gratuitously break support for recent releases, but it
|
|
is sometimes unavoidable. When this occurs, patches contributed by
|
|
the user community to maintain support for older releases will usually
|
|
be committed.
|
|
</P>
|
|
|
|
<P>Each ``port'' listed here
|
|
contains any patches necessary to make the original application source
|
|
code compile and run on FreeBSD. Installing an application is as
|
|
simple as downloading the port, unpacking it and typing
|
|
<A HREF="http://www.freebsd.org/cgi/man.cgi?query=make"><TT>make</TT></A>
|
|
in the port directory. However, the most convenient (and common) method
|
|
is to download the framework for the entire list of ports by installing the
|
|
<!--<A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz">-->
|
|
<A HREF="installing.html">
|
|
entire ports hierarchy</A> at FreeBSD installation time, and then have
|
|
thousands of applications right at your fingertips.
|
|
</P>
|
|
|
|
<P>
|
|
Each port's <TT>Makefile</TT> automatically fetches the
|
|
application source code, either from a local disk, CD-ROM or via
|
|
<A HREF="http://www.freebsd.org/cgi/man.cgi?query=ftp"><TT>ftp</TT></A>,
|
|
unpacks it on your system, applies the patches, and compiles. If
|
|
all went well, a simple <TT>make install</TT> will install the
|
|
application and register it with the package system.</P>
|
|
|
|
<P>For most ports, a precompiled <TT>package</TT> also exists, saving
|
|
the user the work of having to compile anything at all. Each port
|
|
contains a link to its corresponding package and you may either simply
|
|
download that file and then run the
|
|
<A HREF="http://www.freebsd.org/cgi/man.cgi?query=pkg_add"><TT>pkg_add</TT></A>
|
|
command
|
|
on it or you can simply grab the link location and hand it straight
|
|
to <TT>pkg_add</TT> since it is capable of accepting FTP URLs as
|
|
well as filenames.</P>
|
|
|
|
&footer;
|
|
</BODY>
|
|
</HTML>
|