Add Bryan Drewery <bdrewery@FreeBSD.org>' official packages report.

This commit is contained in:
Warren Block 2015-07-20 20:22:51 +00:00
parent cc4740d561
commit 5e0507fc39
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=47029

View file

@ -2844,4 +2844,120 @@
</task>
</help>
</project>
<project cat='ports'>
<title>Official Packages</title>
<contact>
<person>
<name>
<given>Bryan</given>
<common>Drewery</common>
</name>
<email>bdrewery@FreeBSD.org</email>
</person>
<person>
<name>Ports Management Team</name>
<email>portmgr@FreeBSD.org</email>
</person>
<person>
<name>
<given>Sean</given>
<common>Bruno</common>
</name>
<email>sbruno@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://pkg-status.FreeBSD.org">Package Status</url>
</links>
<body>
<p>x86 Packages</p>
<p>With the help of the FreeBSD Foundation providing more
build servers, we have increased the build frequency of
packages from weekly to about every other day. Packages are
provided for all currently supported releases and head on
<tt>i386</tt> and <tt>amd64</tt> from the ports head branch,
and quarterly packages for &os; 10.1 and 9.3 release
branches.</p>
<p>We are using eight different systems for building packages.
The build process has been fully automated and is
more fault tolerant now. More details on this will be
available in an upcoming &os; Journal article. About eleven
servers for daily test builds. To make it simpler for
everyone to find the status and results of these builds, the
<a href="http://pkg-status.FreeBSD.org">pkg-status.FreeBSD.org</a>
has been developed by Bryan Drewery. Its intent is to show
all systems and builds in nearly real-time. It is currently
in a beta stage and will be improved over time. At the time
of this writing, it is temporarily down, but will be restored
soon.</p>
<p>ARM/MIPS Packages</p>
<p>The FreeBSD Foundation purchased servers for the project to
begin building and providing ARM and MIPS packages. These
packages are currently built from x86 systems using QEMU.
More details on this can be found in the
<a href="http://www.bsdcan.org/2015/schedule/events/532.en.html">BSDCan
2015 Presentation</a>. The work to do this has been
shepherded by Sean Bruno and has had help from many people
including but not limited to Juergen Lock, Stacey Son, Ed
Maste, Peter Wemm, Alexander Kabaev, Adrian Chadd, Baptiste
Daroussin, Bryan Drewery, Dimitry Andric, Andrew Turner,
Warner Losh, Ian Lapore, and Brooks Davis.</p>
<p>We are currently targetting packages for head on
<tt>mips</tt>, <tt>mips64</tt> and <tt>armv6</tt>. Each set
takes one to two weeks to build on QEMU. They will be
provided on a best effort basis for now on the default
repository of <tt>pkg.FreeBSD.org</tt>.</p>
</body>
<sponsor>
FreeBSD Foundation (package building hardware)
</sponsor>
<help>
<task>
<p>Portmgr met at BSDCan and decided that the default package
set should be provided based on the Ports Quarterly branch.
This will provide more stable packages by default and allow
users who wish to have the bleeding edge to use the head
packages. The Quarterly branch is currently updated in full
every three months from head and otherwise receives security
and critical fixes. Moving towards this plan will also
require a change to how we update the Quarterly branch.
More details will be provided later.</p>
</task>
<task>
<p>Performance and stability of QEMU continues to improve.
Native cross-building support in ports needs more work and
testing to be viable.</p>
</task>
<task>
<p>The package builds currently run from a <tt>crontab</tt>
every other day. Some of the builds take two hours
(incremental), while others can take up to 30 hours for a
full build. An open task here is to implement a better
OS ABI check to see if incremental builds can be done, or if
a full rebuild is needed when an SA/EN comes out. The plan
for this is detailed at
<a href="https://lists.freebsd.org/pipermail/freebsd-arch/2015-April/017025.html">https://lists.freebsd.org/pipermail/freebsd-arch/2015-April/017025.html</a>.</p>
<p>Another open task is to implement a master queue
coordinator to start the next builds as soon as all others
are done. This will also allow improving the pkg-status
site's view of everything.</p>
</task>
</help>
</project>
</report>