Date: Sat, 9 Nov 2002 15:00:16 -0800 (PST) From: "Bruce A. Mah" <bmah@FreeBSD.ORG> To: freebsd-www@FreeBSD.org Subject: Re: www/45169: suggested update for ports index page on web site Message-ID: <200211092300.gA9N0Gc1081260@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR www/45169; it has been noted by GNATS. From: "Bruce A. Mah" <bmah@FreeBSD.ORG> To: Mark Linimon <linimon@lonesome.com> 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 <tt>make</tt> > -in the port directory. For even greater convenience, you can simply > -install the <a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/branches/-current/por > ts.tar.gz"> > -entire ports hierarchy</a> at installation time (or use > -<a href="../doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup</a > > 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...". > +<a href="ftp://ftp.FreeBSD.org/pub/FreeBSD/branches/-current/ports.tar.gz">; > +ports hierarchy</a> at installation time and then have thousands of > +applications right at your fingertips. You can then use > +<a href="../doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup</a > > > +to track it the master list on an ongoing basis.</p> s/the master list// > > -Each port's <tt>Makefile</tt> automatically fetches the > +<p>Each port's <tt>Makefile</tt> 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 <tt>make install</tt> will install the > @@ -31,11 +32,51 @@ > to <strong>pkg_add</strong> since it's capable of accepting FTP URLs as > well as filenames.</p> > > +<hr> > + > +<H1 ALIGN="LEFT"><FONT COLOR="#660000">Keeping up-to-date</FONT></H1> > + > +<p>There are several options to maintain your collection of packages > +and ports.</p> > +<ul> > +<li>One possibility is to stay entirely with binaries and merely > + download individual packages as needed.</li> > +<li>For those unafraid to compile from source, by far the most popular > + method is to download and use the <tt>portupgrade</tt> port. In the docs we make hyperlinks to ports...this might be useful, e.g.: <a href="http://www.freebsd.org/cgi/url.cgi?ports/sysutils/portupgrade/pkg-descr"><tt>sysutils/portupgrade</tt></a>; Maybe doing this on the first reference might be helpful. > + <tt>portupgrade</tt> works by using the underlying <tt>pkg_*</tt> > + 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. <tt>portupgrade</tt> may be > + run interactively or in batch mode; it's not necessary to be tracking > + any other FreeBSD sources to use it, either.</li> > +<li>For those that are already rebuilding their entire system > + from source, they may wish to grab ports via > + <a href="../doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup< > /a>. > + </li> > +<li>Finally, individual ports may be added via <tt>pkg_add</tt>. > + Most people will probably choose one of the above methods; > + however, using <tt>pkg_add</tt> can sometimes be necessary, > + e.g. in certain cases where <tt>portupgrade</tt> refuses > + to upgrade itself.</li> 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. > +</ul> > + > +<p> > +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 > +<tt>ports/Mk</tt>. 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 <strong>cvsup</strong>, this > +means you need <tt>ports-base</tt> in your cvsupfile.) If you still > +see errors even with the latest <tt>bsd.port.mk</tt> and friends, > +please fetch the entire collection. > +</p> > + > <p>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 > <a href="http://www.FreeBSD.org/cgi/ports.cgi">FreeBSD Ports Changes</a> > -page.</p> > +on this site; alternatively, you may wish to either browse (or subscribe to) > +the lists at <a href="http://www.freshports.org">www.freshports.org</a>.</p>; > > <FORM METHOD="GET" ACTION="http://www.FreeBSD.org/cgi/ports.cgi">; > Search for: > @@ -58,17 +99,6 @@ > <hr> > > <H1 ALIGN="LEFT"><FONT COLOR="#660000">Upgrade kits</FONT></H1> > - > -<p> > -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 > -<tt>ports/Mk</tt>. (If you are using <strong>cvsup</strong>, this > -means you need <tt>ports-base</tt> in your cvsupfile.) If you still > -see errors even with the latest <tt>bsd.port.mk</tt> and friends, > -please fetch the entire collection. > -</p> > > <p> > The current ports tree officially supports only FreeBSD-current and Bruce. --==_Exmh_-443680114P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) Comment: Exmh version 2.5+ 20020506 iD8DBQE9zZF02MoxcVugUsMRAlx3AJ9s5IzDLE9NBttWmKCDReULNSiBXQCfZ0Tw 5briWNN1mo+rJLCG3IQLrr4= =06jA -----END PGP SIGNATURE----- --==_Exmh_-443680114P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-www" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211092300.gA9N0Gc1081260>