Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 May 2007 22:07:12 +0200
From:      Ivan Voras <ivoras@fer.hr>
To:        freebsd-hackers@freebsd.org
Subject:   Re: Looking for speed increases in "make index" and pkg_version for ports
Message-ID:  <f3fcpk$30t$1@sea.gmane.org>
In-Reply-To: <465B02C4.2020508@math.missouri.edu>
References:  <4659EF80.70100__16104.363036766$1180300054$gmane$org@math.missouri.edu>	<f3cuvl$3q5$1@sea.gmane.org> <465B02C4.2020508@math.missouri.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig279D4A02D1F67CF59DE01083
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Stephen Montgomery-Smith wrote:
> Ivan Voras wrote:

>> As long as far-out ideas are being discussed, how about caching such
>> information (including dependenices) in a file (I'd call it a database=

>> but then I'd had to start a holy war :) ) so it's calculated only once=
,
>> preferably on the portsnap / cvsup servers and not at the end-user?
>=20
> Because the information is not a constant.  For example, the mpg123 por=
t
> changes its PKGNAME as soon as esound is installed.

Maybe the time has come to give up on some of the flexibility the ports
tree has (and this particular one is confusing to the users) in favour
of gaining speed?


--------------enig279D4A02D1F67CF59DE01083
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.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGWzZwldnAQVacBcgRAs5mAJ9Qw+s+kU+gip4rYavVInmUpLwWFwCgjq2A
A8HqGLyhECWg8LK1hNceMWA=
=dkcU
-----END PGP SIGNATURE-----

--------------enig279D4A02D1F67CF59DE01083--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f3fcpk$30t$1>