speed up port compiling using RAM (tmpfs) ???

Peter Jeremy PeterJeremy at optushome.com.au
Sat Jan 21 13:10:00 PST 2006

On Sat, 2006-Jan-21 14:30:57 -0600, Matthew D. Fuller wrote:
>On Sat, Jan 21, 2006 at 03:23:21PM -0500 I heard the voice of
>Kris Kennaway, and lo! it spake thus:
>> On Sat, Jan 21, 2006 at 10:07:39AM -0600, Matthew D. Fuller wrote:
>> > 
>> > This is something that may be easier to:
>> > 
>> > 3) Implement in portupgrade or portmanager or some such higher-level
>> >    tool in a language that gives a little more flexibility than make,
>> >    and which is already apparently pulling in most of the information
>> >    it may need to do the job.
>> You still have the same issue as 1).
>  [ 1 == building dependancy tree to know what depends on what ]
>Yes, but portupgrade and friends already do most of that, so they can
>upgrade stuff "in order".

Actually, they rely on there being an up-to-date INDEX file and build
their own dependency database from that.  Actually building the INDEX
file is non-trivial (it takes roughly an hour for me).  Tools like
p5-FreeBSD-Portindex-1.4 cache intermediate output from "make index"
but still have the up-front "make index" cost (and the documentation
recommends a full "make index" regularly).  You can save time by
fetching the INDEX, but then you can't be certain that it matches your
ports tree or your port options.

Given that a port's dependency tree can depend on the options it is
invoked with, it would be nicer if the dependency tree was generated
dynamically, rather than pulled out of the latest INDEX file.  If
the INDEX dependencies are used to generate a parallel build tree
then it's still important that the actual build process has interlocks
to prevent unforeseen dependencies causing clashes.

Peter Jeremy

More information about the freebsd-hackers mailing list