What are we doing wrong that is causing it to take such a long
    time?  I've noticed when I've tried to do it that sometimes the bulk
    build gets stuck on ftp.  It can come to a complete halt and stay that
    way for hours on end :-(

    For 2.0 we really need to have working packages on release day.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>
[ message continues ]

That long period of time is caused by doing a full build, from scratch. 
It can get much shorter in subsequent builds, though that doesn't directly
help us.  On a more positive note, I haven't seen any of those complete
FTP halts with this build, and a lot of the hanging issues that were in
the 2008Q1 release are gone - notably python24, which would always kill
the build.

I know Joerg's used VMWare to simulate multiple hosts building pkgsrc,
though I recall him saying something about how that wouldn't work out over
multiple separate hosts (i.e. distributed over multiple locations)  I have
not tried it yet, and I don't know how much of a speed improvement it
gains.

I'll do my best to get it together; I had wanted to get the new site
together for the release too, but my job is overriding my free time,
especially this week of all weeks.  (SoC surveys are due too, dammit.)



[ message continues ]

Mostly a side effect of bad concurrency in the kernel and lack of

I wouldn't do it for a non-local setup. But with a quad core it should
push build time quite a bit under on week. Depending on memory etc, it
might be good enough for a dual core to do native builds and having more
jobs than cpus helps to avoid stalls.

Joerg
[ message continues ]

When I did experimental bulk builds, I did observe problems with 
stalling FTP, so I added the following line to /usr/pkg/etc/mk.conf 
(this is actually part of the bootstrap kit):
FETCH_BEFORE_ARGS=-q 60
 From the ftp(1) man page:
     -q quittime
                 Quit if the connection has stalled for quittime seconds.

[ message continues ]

Sadly it doesn't work reliably.

Joerg
[ message continues ]

http://pkgbox.dragonflybsd.org/packages/DragonFly-2.0/pkgsrc-2008Q2/ is
now full of binary packages.

There's some older and newer packages in there, and a good chunk of them
were built very recently on 1.13, so there will be a harmless version
warning when installed.

However, as soon as the full bulk build I'm running completes, the new 2.0
packages will be installed, and all out of date ones removed.  So we are
covered for binary installs at time of release if the pbulk build hasn't
completed.

[ message continues ]