package build process
dillon at backplane.com
Wed Aug 31 14:38:41 PDT 2016
Well, we actually dedicate two blades to doing nothing but package
building, and we can use a more substantial server if we need to get it
done faster (the record is roughly 22 hours for a full bulk build on the
dual-xeon or the 48-core opteron box). There's also a lot of bulk building
going on under-the-hood to test and stage updates before they hits
distribution channels and become user-visible. That actually isn't the
The real problem is that there are so many package dependencies for
something like mysql that keeping up with the latest release and still
making sure that all the dependent ports build is a real chore. And, I
should also say, that DragonFlyBSD and FreeBSD both use essentially the
same base ports and we have devs with commit access to both projects. So a
large chunk of the package updates should be credited to the FreeBSD devs,
and a large chunk is a joint effort.
(Which I'm very happy about because... well, think about how much work is
involved in maintaining 24000+ packages!)
On Mon, Aug 29, 2016 at 1:14 PM, jungle Boogie <jungleboogie0 at gmail.com>
> On 29 August 2016 at 12:15, John Marino <dragonflybsd at marino.st> wrote:
> > No. We don't rebuild *ALL* packages every time, only the ones that
> > it. It's called incremental building.
> So that means you update packages and its dependencies? I'm asking
> because I noticed sqlite3 was not updated but there was a release of
> 3.14.0 on 8th of August. There's now a 3.14.1 release from the 11th.
> By the way, I'm very appreciative of and for the packaging of all
> these packages. Updating 13,900+ ports in 3 days is very intensive on
> your system that could be utilized for something else. Thank you!
> inum: 883510009027723
> sip: jungleboogie at sip2sip.info
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users