Date: Mon, 28 May 2007 11:26:44 -0500 From: Stephen Montgomery-Smith <stephen@math.missouri.edu> To: Ivan Voras <ivoras@fer.hr> Cc: freebsd-hackers@freebsd.org Subject: Re: Looking for speed increases in "make index" and pkg_version for ports Message-ID: <465B02C4.2020508@math.missouri.edu> In-Reply-To: <f3cuvl$3q5$1@sea.gmane.org> References: <4659EF80.70100__16104.363036766$1180300054$gmane$org@math.missouri.edu> <f3cuvl$3q5$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Voras wrote: > Stephen Montgomery-Smith wrote: >> I have been thinking a lot about looking for speed increases for "make >> index" and pkg_version and things like that. So for example, in >> pkg_version, it calls "make -V PKGNAME" for every installed package. Now >> "make -V PKGNAME" should be a speedy operation, but the make has to load >> in and analyze bsd.port.mk, a quite complicated file with about 200,000 >> characters in it, when all it is needing to do is to figure out the >> value of the variable PKGNAME. > > 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? Because the information is not a constant. For example, the mpg123 port changes its PKGNAME as soon as esound is installed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465B02C4.2020508>