Date: Tue, 24 Jan 2006 19:19:37 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: make index Message-ID: <43D67DC9.5030509@infracaninophile.co.uk> In-Reply-To: <20060124190159.GH29457@tigger.digitaltorque.ca> References: <20060124190159.GH29457@tigger.digitaltorque.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA0393802A60F28C52C06AA4D
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Michael P. Soulier wrote:
> After running CVSup, I've seen people build their "index" via
>=20
> cd /usr/ports
> make index
> # wait a frickin' long time
>=20
> What is the index, and does it really require rebuilding after each CVS=
up?
The index is a list of all of the ports, what each port depends on, who
the maintainer is and various other data.  It's used by the 'make search'=
command (see ports(7)) an a few other make targets you can invoke from
/usr/ports, plus it's used quite extensively by portupgrade(8).  Other
port maintenance software does not need an index file -- generally they
work out the dependency relations between different packages on the fly.
You don't need to keep running 'make index' all the time.  Firstly, you
can download a freshly build index by 'make fetchindex' -- which is
sufficient for most uses. If you use the new portsnap(1) facility
instead of cvsup(1), you'll get a freshly built index file included
automatically.  Or (blowing my own trumpet here...) you can install
sysutils/p5-FreeBSD-Portindex which gives you a method of incrementally
updating your index file based on what was modified during the previous
cvsup session (or however you choose to upgrade your ports).
	Cheers,
	Matthew
--=20
Dr Matthew J Seaman MA, D.Phil.                       Flat 3
                                                      7 Priory Courtyard
PGP: http://www.infracaninophile.co.uk/pgpkey         Ramsgate
                                                      Kent, CT11 9PW, UK
--------------enigA0393802A60F28C52C06AA4D
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD1n3P8Mjk52CukIwRA0zwAJ4zVD4paArza0C2J1dV2FkVhDNWMgCfR6D1
X8TlP21efkuIIZ45TzWgXQI=
=X1c7
-----END PGP SIGNATURE-----
--------------enigA0393802A60F28C52C06AA4D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43D67DC9.5030509>
