From owner-freebsd-www Sat Nov 9 12:20: 6 2002 Delivered-To: freebsd-www@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17FA637B401 for ; Sat, 9 Nov 2002 12:20:03 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29FE543E75 for ; Sat, 9 Nov 2002 12:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gA9KK2x3017144 for ; Sat, 9 Nov 2002 12:20:02 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gA9KK1MJ017143; Sat, 9 Nov 2002 12:20:01 -0800 (PST) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC8D637B401 for ; Sat, 9 Nov 2002 12:19:43 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFD0A43E3B for ; Sat, 9 Nov 2002 12:19:42 -0800 (PST) (envelope-from linimon@lonesome.com) Received: from lonesome.lonesome.com (cs2876-77.austin.rr.com [24.28.76.77]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id A200614314 for ; Sat, 9 Nov 2002 14:19:36 -0600 (CST) Received: from lonesome.lonesome.com (localhost.lonesome.com [127.0.0.1]) by lonesome.lonesome.com (8.12.6/8.12.3) with ESMTP id gA9LKcYW095753 for ; Sat, 9 Nov 2002 15:20:38 -0600 (CST) (envelope-from linimon@lonesome.lonesome.com) Received: (from linimon@localhost) by lonesome.lonesome.com (8.12.6/8.12.6/Submit) id gA9LKcVg095752; Sat, 9 Nov 2002 15:20:38 -0600 (CST) (envelope-from linimon) Message-Id: <200211092120.gA9LKcVg095752@lonesome.lonesome.com> Date: Sat, 9 Nov 2002 15:20:38 -0600 (CST) From: Mark Linimon To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113.1 Subject: www/45169: suggested update for ports index page on web site Sender: owner-freebsd-www@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 45169 >Category: www >Synopsis: suggested update for ports index page on web site >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-www >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Nov 09 12:20:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Mark Linimon >Release: FreeBSD-4.7 >Organization: FreeBSD >Environment: System: FreeBSD lonesome.lonesome.com 4.7-STABLE FreeBSD 4.7-STABLE #0: Fri Nov 8 23:46:29 CST 2002 root@lonesome.lonesome.com:/usr/src/sys/compile/MULTIMEDIA i386 >Description: The ports page doesn't currently point to portupgrade as the "start here" solution for most users. Also, the explanation of maintaining the list of ports, vs maintaining the ports themselves, is a little tangled. >How-To-Repeat: N/A >Fix: The following suggested fix to /usr/www/en/ports/ports.inc attempts to move around some of the existing text (to move to how-to details until after the introductory matter is given) and to add an overview of options for maintaing an entire collection. This clarifies the presentation to those new to the FreeBSD ports system (everybody else already knows this stuff already). --- ports.inc.dist Thu Jul 11 09:51:43 2002 +++ ports.inc Sat Nov 9 15:12:30 2002 @@ -10,14 +10,15 @@ 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 make -in the port directory. For even greater convenience, you can simply -install the -entire ports hierarchy at installation time (or use -CVSup to track it on -an ongoing basis) and have thousands of applications right at your -fingertips. +in the port directory. However, the most convenient (and common) method +is to download the ``master list'' of ports by installing the + +ports hierarchy at installation time and then have thousands of +applications right at your fingertips. You can then use +CVSup +to track it the master list on an ongoing basis.

-Each port's Makefile automatically fetches the +

Each port's Makefile automatically fetches the application source code, either from a local disk, CDROM or via ftp, unpacks it on your system, applies the patches, and compiles. If all went well, a simple make install will install the @@ -31,11 +32,51 @@ to pkg_add since it's capable of accepting FTP URLs as well as filenames.

+
+ +

Keeping up-to-date

+ +

There are several options to maintain your collection of packages +and ports.

+
    +
  • One possibility is to stay entirely with binaries and merely + download individual packages as needed.
    • +
  • For those unafraid to compile from source, by far the most popular + method is to download and use the portupgrade port. + portupgrade works by using the underlying pkg_* + commands but hides most of their complexity. There is a handy + option for maintaining and updating all currently installed ports, + in addition to just individual ones. portupgrade may be + run interactively or in batch mode; it's not necessary to be tracking + any other FreeBSD sources to use it, either.
    • +
  • For those that are already rebuilding their entire system + from source, they may wish to grab ports via + CVSup. +
    • +
  • Finally, individual ports may be added via pkg_add. + Most people will probably choose one of the above methods; + however, using pkg_add can sometimes be necessary, + e.g. in certain cases where portupgrade refuses + to upgrade itself.
    • +
+ +

+The ports listed on these web pages are continually being updated. +It is recommended that you refresh the entire collection together, as +many ports depend on other parts of the tree. If that is not +possible, at least make sure you get the latest make macro files in +ports/Mk. (If you are using cvsup, this +means you need ports-base in your cvsupfile.) If you still +see errors even with the latest bsd.port.mk and friends, +please fetch the entire collection. +

+

For more information about new, changed or removed ports/packages, or if you wish to search for a specific application to see if it's -available as a port/package, please see the +available as a port/package, you may browse the FreeBSD Ports Changes -page.

+on this site; alternatively, you may wish to either browse (or subscribe to) +the lists at www.freshports.org.

Search for: @@ -58,17 +99,6 @@

Upgrade kits

- -

-The ports listed on these web pages are continually being updated. -It is recommended that you refresh the entire collection together, as -many ports depend on other parts of the tree. If that is not -possible, at least make sure you get the latest make macro files in -ports/Mk. (If you are using cvsup, this -means you need ports-base in your cvsupfile.) If you still -see errors even with the latest bsd.port.mk and friends, -please fetch the entire collection. -

The current ports tree officially supports only FreeBSD-current and >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-www" in the body of the message