From owner-freebsd-www Sat Nov 9 15: 0:21 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 183C437B401
for ; Sat, 9 Nov 2002 15:00:17 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
by mx1.FreeBSD.org (Postfix) with ESMTP id 9F67543E77
for ; Sat, 9 Nov 2002 15:00:16 -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 gA9N0Gx3081261
for ; Sat, 9 Nov 2002 15:00:16 -0800 (PST)
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gA9N0Gc1081260;
Sat, 9 Nov 2002 15:00:16 -0800 (PST)
Date: Sat, 9 Nov 2002 15:00:16 -0800 (PST)
Message-Id: <200211092300.gA9N0Gc1081260@freefall.freebsd.org>
To: freebsd-www@FreeBSD.org
Cc:
From: "Bruce A. Mah"
Subject: Re: www/45169: suggested update for ports index page on web site
Reply-To: "Bruce A. Mah"
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
The following reply was made to PR www/45169; it has been noted by GNATS.
From: "Bruce A. Mah"
To: Mark Linimon
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: www/45169: suggested update for ports index page on web site
Date: Sat, 09 Nov 2002 14:51:33 -0800
--==_Exmh_-443680114P
Content-Type: text/plain; charset=us-ascii
If memory serves me right, Mark Linimon wrote:
> >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.
Additional background info for this PR: Someone (not the PR originator)
managed to mess up their installed ports because they apparently tried
to run the output of "pkg_version -c" as an output tool, despite
multiple admonitions to the contrary.
OK. Generally, I liked this change, although a more ports-oriented
person should probably also weigh in on it too. More specific comments
follow in-line:
> --- 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
I'd get rid of "master list"...this sounds to me like ports/INDEX.
Maybe just say "...download and install 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.
s/the master list//
>
> -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.
In the docs we make hyperlinks to ports...this might be useful, e.g.:
sysutils/portupgrade
Maybe doing this on the first reference might be helpful.
> + 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<
> /a>.
> +
> +- 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.
This isn't a good updating method, though it certainly works well for
installing new ports. I don't think I've ever had a case where
portupgrade couldn't update 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.
You really want to update everything together, in case there are
infrastructure changes that somehow break old ports. (I can't think
of a good example of this happening, however.)
> (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.
>
>