svn commit: r40615 - head/en_US.ISO8859-1/htdocs/news/status
Glen Barber
gjb at FreeBSD.org
Sun Jan 13 19:31:57 UTC 2013
Author: gjb
Date: Sun Jan 13 19:31:56 2013
New Revision: 40615
URL: http://svnweb.freebsd.org/changeset/doc/40615
Log:
Add the April-June 2012 status report.
Prepared by: pgj
Minor tweaks by: gjb
Added:
head/en_US.ISO8859-1/htdocs/news/status/report-2012-04-2012-06.xml (contents, props changed)
Added: head/en_US.ISO8859-1/htdocs/news/status/report-2012-04-2012-06.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2012-04-2012-06.xml Sun Jan 13 19:31:56 2013 (r40615)
@@ -0,0 +1,1005 @@
+<?xml version="1.0" encoding="iso-8859-1" ?>
+<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status
+Report//EN" "http://www.FreeBSD.org/XML/www/share/xml/statusreport.dtd">
+<!-- $FreeBSD$ -->
+<report>
+ <date>
+ <month>April-June</month>
+
+ <year>2012</year>
+ </date>
+
+ <section>
+ <title>Introduction</title>
+
+ <p>This report covers &os;-related projects between April and June
+ 2012. This is the second of the four reports planned for
+ 2012.</p>
+
+ <p>Thanks to all the reporters for the excellent work! This report
+ contains 17 entries and we hope you enjoy reading it.</p>
+
+ <p>Please note that the deadline for submissions covering the period
+ between July and December 2012 is January 15th, 2013.</p>
+ </section>
+
+ <category>
+ <name>proj</name>
+
+ <description>Projects</description>
+ </category>
+
+ <category>
+ <name>bin</name>
+
+ <description>Userland Programs</description>
+ </category>
+
+ <category>
+ <name>team</name>
+
+ <description>&os; Team Reports</description>
+ </category>
+
+ <category>
+ <name>kern</name>
+
+ <description>Kernel</description>
+ </category>
+
+ <category>
+ <name>net</name>
+
+ <description>Network Infrastructure</description>
+ </category>
+
+ <category>
+ <name>docs</name>
+
+ <description>Documentation</description>
+ </category>
+
+ <category>
+ <name>arch</name>
+
+ <description>Architectures</description>
+ </category>
+
+ <category>
+ <name>ports</name>
+
+ <description>Ports</description>
+ </category>
+
+ <category>
+ <name>misc</name>
+
+ <description>Miscellaneous</description>
+ </category>
+
+ <project cat='arch'>
+ <title>&os;/arm on ARM Fast Models Simulator for Cortex-A15 MPCore
+ Processor</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Zbigniew</given>
+ <common>Bodek</common>
+ </name>
+ <email>zbb at semihalf.com</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Rafal</given>
+ <common>Jaworowski</common>
+ </name>
+ <email>raj at semihalf.com</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Tomasz</given>
+ <common>Nowicki</common>
+ </name>
+ <email>tn at semihalf.com</email>
+ </person>
+ </contact>
+
+ <links>
+ <url
+ href="http://www.arm.com/products/processors/cortex-a/cortex-a15.php">Cortex-A15 product page</url>
+ <url
+ href="http://www.arm.com/products/tools/models/fast-models.php">Fast Models product page</url>
+ </links>
+
+ <body>
+ <p>ARM Fast Models is platform which helps software developers
+ debug systems in parallel with SoC design, speeding up and
+ improving system development. This work is bringing up &os; on
+ ARM Fast Models system based on ARM Cortex-A15 and peripheral
+ components. It works in single user mode, using a compiled-in
+ kernel RAM disk minimal root file system.</p>
+
+ <p>Current &os; support includes:</p>
+
+ <ul>
+ <li>L1, L2 cache, Branch Predictor</li>
+ <li>Dual-core (SMP) support setup in WB cache mode</li>
+ <li>Cortex-A15 integrated Generic Timer</li>
+ <li>Drivers for ARM peripheral components:
+ <ul>
+ <li>PL011 UART controller</li>
+ <li>PL390 GIC - Generic Interrupt Controller</li>
+ <li>SP804 Dual Timer</li>
+ </ul>
+ </li>
+ </ul>
+
+ <p>Next steps:</p>
+
+ <ul>
+ <li>Quad-core (SMP) support</li>
+ <li>Multi-user mode</li>
+ </ul>
+ </body>
+ </project>
+
+ <project cat='kern'>
+ <title>&os;/at91 Improvements</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Warner</given>
+ <common>Losh</common>
+ </name>
+ <email>imp at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url
+ href="http://wiki.freebsd.org/FreeBSDAtmel">&os; on ATMEL AT91 Wiki</url>
+ </links>
+
+ <body>
+ <p>&os;'s Atmel support has languished for some time. A number of
+ improvements were urgently needed as demand for newer SoCs has
+ materialized. New SoC support is not hard, but it does wind up
+ copying a lot of code. I have started down the path to make it
+ easier to do. I had planned on making it table driven. But
+ then I discovered with dts files that Atmel was producing.</p>
+
+ <p>So, I plan on moving to using Atmel's <tt>.dsti</tt> files, or
+ variations on them. They have .dsti files for all the AT91SAM9
+ parts. This should allow us to support new SoCs and boards
+ faster.</p>
+
+ <p>However, there are some challenges with this approach. Pin
+ multiplexing seems undefined in Atmel's dts file. Only a few of
+ the devices are well-defined at the present time. And the
+ encoding seems to be immature.</p>
+
+ <p>So we have a target-rich port that is quite ripe for
+ refactoring.</p>
+ </body>
+
+ <help>
+ <task>Update the base system libfdt to a version that supports
+ include.</task>
+ <task>Write a <tt>.dtsi</tt> for Atmel AT91RM9200.</task>
+ <task>Write <tt>.dti</tt> files for all supported boards.</task>
+ <task>Help sort out the pin multiplexing issue.</task>
+ <task>Refactor existing board files to make new ones easier in the
+ interim.</task>
+ <task>Knock yourself out and implement board support for new
+ CPUs.</task>
+ </help>
+ </project>
+
+ <project cat='misc'>
+ <title>BSD-Day 2012</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Gábor</given>
+ <common>Páli</common>
+ </name>
+ <email>pgj at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://bsdday.eu/2012">BSD-Day 2012 web site</url>
+ <url
+ href="http://www.youtube.com/playlist?list=PL13D5471D8ECF08C9">Video recordings of the talks at YouTube</url>
+ <url
+ href="https://picasaweb.google.com/116452848880746560170/BSDDay2012?authkey=Gv1sRgCN3twLrxuaeongE">Event photo album</url>
+ </links>
+
+ <body>
+ <p>For this year, we moved the time of the event earlier by six
+ months, so it was held on May 5, 2012 and it was co-located with
+ the Austrian Linuxweeks (Linuxwochen Österreich) in Vienna.
+ We had many sponsors, like the freshly joined &os; Foundation,
+ iXsystems, FreeBSDMall, BSD Magazine, allBSD.de Projekt, that
+ enabled us to continue our previously launched series of
+ multi-project BSD developer summits all around Central
+ Europe.</p>
+
+ <p>To kick off, there was a "stammtisch" (local beer meetup)
+ organized in the downtown of Vienna, at Kolar on the Friday
+ evening before the event — as usual. Then it was followed
+ by the event on Saturday that brought many interesting topics
+ from the world of &os;, OpenBSD and NetBSD: running NetBSD as an
+ embedded system for managing VOIP applications, introduction to
+ the Capsicum security framework, relayd(8), the load balancer
+ and proxy solution for OpenBSD, status update of the
+ developments around the &os; ports tree, using DVCSs in clouds,
+ firewalling with pfSense, and mfsBSD. Please consult the links
+ in the report for the details.</p>
+ </body>
+ </project>
+
+ <project cat='team'>
+ <title>The &os; Core Team</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Core Team</given>
+ </name>
+ <email>core at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url
+ href="http://docs.FreeBSD.org/cgi/mid.cgi?1342030291.6001.80.camel">Announcement</url>
+ </links>
+
+ <body>
+ <p>The &os; Project is pleased to announce the completion of the
+ 2012 Core Team election. The &os; Core Team acts as the
+ project's "Board of Directors" and is responsible for approving
+ new src committers, resolving disputes between developers,
+ appointing sub-committees for specific purposes (security
+ officer, release engineering, port managers, webmaster, et
+ cetera), and making any other administrative or policy decisions
+ as needed. The Core Team has been elected by &os; developers
+ every 2 years since 2000.</p>
+
+ <p>Peter Wemm rejoins the Core Team after a two-year hiatus, with
+ new members Thomas Abthorpe, Gavin Atkinson, David Chisnall,
+ Attilio Rao and Martin Wilke joining incumbents John Baldwin,
+ Konstantin Belousov and Hiroki Sato.</p>
+
+ <p>The complete newly elected core team is:</p>
+
+ <ul>
+ <li>Thomas Abthorpe <tabthorpe at FreeBSD.org></li>
+ <li>Gavin Atkinson <gavin at FreeBSD.org></li>
+ <li>John Baldwin <jhb at FreeBSD.org></li>
+ <li>Konstantin Belousov <kib at FreeBSD.org></li>
+ <li>David Chisnall <theraven at FreeBSD.org></li>
+ <li>Attilio Rao <attilio at FreeBSD.org></li>
+ <li>Hiroki Sato <hrs at FreeBSD.org></li>
+ <li>Peter Wemm <peter at FreeBSD.org></li>
+ <li>Martin Wilke <miwi at FreeBSD.org></li>
+ </ul>
+
+ <p>The new Core Team would like to thank outgoing members Wilko
+ Bulte, Brooks Davis, Warner Losh, Pav Lucistnik, Colin Percival
+ and Robert Watson for their service over the past two (and in
+ some cases, many more) years.</p>
+
+ <p>The Core Team would also especially like to thank Dag-Erling
+ Smørgrav for running the election.</p>
+ </body>
+</project>
+
+ <project cat='docs'>
+ <title>The &os; Japanese Documentation Project</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Hiroki</given>
+ <common>Sato</common>
+ </name>
+ <email>hrs at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Ryusuke</given>
+ <common>Suzuki</common>
+ </name>
+ <email>ryusuke at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web Page</url>
+ <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese Documentation Project Web Page</url>
+ </links>
+
+ <body>
+ <p>Our translation work has slightly moved on to handbook from the
+ <tt>www/ja</tt> (CVS) or <tt>htdocs</tt> (SVN) subtree, since
+ almost translated web page contents were updated to the latest
+ English counterparts.</p>
+
+ <p>During this period, we translated the 8.3-RELEASE announcement
+ and published it in a timely manner. Newsflash and some other
+ updates in the English version were also translated as soon as
+ possible.</p>
+
+ <p>For &os; Handbook, translation work of the "cutting-edge" and
+ "printing" sections have been completed. Some updates in the
+ "linuxemu" and "serialcomms" section were done. At this moment,
+ "bsdinstall", "cutting-edge", "desktop", "install",
+ "introduction", "kernelconfig", "mirrors", "multimedia",
+ "pgpkeys", "ports", "printing", and "x11" chapters are
+ synchronized with the English versions.</p>
+ </body>
+
+ <help>
+ <task>Further translation work of outdated documents in
+ <tt>ja_JP.eucJP</tt> subtree.</task>
+ </help>
+ </project>
+
+ <project cat='team'>
+ <title>&os; Documentation Project</title>
+
+ <contact>
+ <person>
+ <email>freebsd-doc at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://wiki.freebsd.org/GoogleCodeIn/2011Status"/>
+ <url href="http://wiki.freebsd.org/201208DevSummit"/>
+ <url href="http://wiki.freebsd.org/DocIdeaList"/>
+ </links>
+
+ <body>
+ <p>We continue to make progress in committing the work produced as
+ part of Google Code-In 2011; an overview of the status is at <a
+ href="http://wiki.freebsd.org/GoogleCodeIn/2011Status">http://wiki.freebsd.org/GoogleCodeIn/2011Status</a>.
+ Doc committers and GCIN mentors are encouraged to go through the
+ list and help shepherd outstanding tasks into the tree.</p>
+
+ <p>We are planning a full day of Documentation Summit on the day
+ preceding the August 2012 DevSummit in Cambridge, UK. This
+ follows a successful DocSummit day held at BSDCan in May 2012.
+ Further details are available at: <a
+ href="http://wiki.freebsd.org/201208DevSummit">http://wiki.freebsd.org/201208DevSummit</a>.</p>
+
+ <p>A doc sprint took place over IRC (<tt>#bsddocs on</tt> EFnet)
+ in early July, setting out plans for reviving the marketing team
+ and a strong desire for a new, more organized website.</p>
+
+ <p>A lot of progress and momentum has built up with creating and
+ updating documentation and website content over the last few
+ months. Also read the doceng report for the recent
+ infrastructure improvements.</p>
+
+ <p>Anyone wishing to help with this effort is welcome to join us
+ and say hello either on the freebsd-doc mailing list, or
+ <tt>#bsddocs</tt> on EFnet IRC.</p>
+ </body>
+
+ <help>
+ <task>Review the website content and remove outdated parts or
+ update when applicable.</task>
+
+ <task>Go through the doc idea list on the wiki and start working
+ them out.</task>
+ </help>
+ </project>
+
+ <project cat='bin'>
+ <title>&os; Services Control (fsc)</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Tom</given>
+ <common>Rhodes</common>
+ </name>
+ <email>trhodes at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>FSC has been moved into the ports system (see
+ <tt>sysutils/fsc</tt>) and continues to improve outside of the
+ ports tree. Some interesting work is being done in the area of
+ services control, system boot, and a simplification of the
+ process. Stay tuned for more information in status reports that
+ follow.</p>
+ </body>
+
+ <help>
+ <task>Test, test, test. Feedback is really important to this
+ project.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>&os; Haskell Ports</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Gábor</given>
+ <common>PÁLI</common>
+ </name>
+ <email>pgj at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Ashish</given>
+ <common>SHUKLA</common>
+ </name>
+ <email>ashish at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url
+ href="http://wiki.freebsd.org/Haskell">&os; Haskell wiki page</url>
+ <url
+ href="https://github.com/freebsd-haskell/freebsd-haskell/">&os; Haskell ports repository</url>
+ </links>
+
+ <body>
+ <p>We are proud to announce that the &os; Haskell Team has updated
+ the Haskell Platform to 2012.2.0.0, GHC to 7.4.1 as well as
+ updated existing ports to their latest stable versions. We also
+ added a number of new Haskell ports, and their count in &os;
+ Ports tree is now 336.</p>
+ </body>
+
+ <help>
+ <task>Test GHC to work with clang/LLVM.</task>
+ <task>Add an option to the <tt>lang/ghc</tt> port to be able to
+ build it with already installed GHC instead of requiring a
+ separate GHC bootstrap tarball.</task>
+ <task>Commit pending Haskell ports to the &os; Ports tree.</task>
+ <task>Add more ports to the Ports Collection.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>KDE/&os;</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>KDE</given>
+ <common>FreeBSD</common>
+ </name>
+ <email>kde at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://FreeBSD.kde.org">KDE/&os; home page</url>
+ <url href="http://FreeBSD.kde.org/area51.php">area51</url>
+ </links>
+
+ <body>
+ <p>The team has made many releases and upstreamed many fixes and
+ patches. The latest round of releases include:</p>
+
+ <ul>
+ <li>KDE SC: 4.8.3, 4.8.4 (in ports) and 4.8.95 (in area51)</li>
+ <li>Qt: 4.8.1, 4.8.2</li>
+ <li>PyQt: 4.9.1; SIP: 4.13.2; QScintilla 2.6.1</li>
+ <li>KDevelop: 2.3.1; KDevPlatform: 1.3.1</li>
+ <li>Calligra: 2.4.2, 2.4.3</li>
+ <li>Amarok: 2.5.90 (in area51)</li>
+ <li>CMake: 2.8.8</li>
+ <li>Digikam (and KIPI-plugins): 2.6.0</li>
+ </ul>
+
+ <p>As a result — according to PortScout — kde@ has 393
+ ports, of which 91% are up-to-date.</p>
+
+ <p>The team is always looking for more testers and porters so
+ please contact us and visit our home page.</p>
+ </body>
+
+ <help>
+ <task>Test KDE SC 4.8.95.</task>
+ <task>Test KDE PIM 4.8.95.</task>
+ <task>Update out-of-date ports, see <a
+ href="http://portscout.org/kde@freebsd.org.html">PortScout</a> for a
+ list.</task>
+ </help>
+ </project>
+
+ <project cat='net'>
+ <title>Multipath TCP (MPTCP) for &os;</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Nigel</given>
+ <common>Williams</common>
+ </name>
+ <email>njwilliams at swin.edu.au</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Lawrence</given>
+ <common>Stewart</common>
+ </name>
+ <email>lastewart at swin.edu.au</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Grenville</given>
+ <common>Armitage</common>
+ </name>
+ <email>garmitage at swin.edu.au</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://caia.swin.edu.au/newtcp/mptcp/"/>
+ <url
+ href="http://tools.ietf.org/html/draft-ietf-mptcp-multiaddressed-09">TCP Extensions for Multipath Operation with Multiple Addresses (draft)</url>
+ <url
+ href="http://mptcp.info.ucl.ac.be/">"MultiPath TCP — Linux Kernel implementation" home page</url>
+ </links>
+
+ <body>
+ <p>Work is underway to create an IETF draft-compatible Multipath
+ TCP implementation for the &os; kernel.</p>
+
+ <p>A key goal of the project is to create a research platform to
+ investigate a range of multipath related transport issues
+ including congestion control, retransmission strategy and packet
+ scheduling policy. We also aim to provide full interoperability
+ with the Linux kernel implementation being developed at
+ Université catholique de Louvain.</p>
+
+ <p>We expect to release code and results at the project's home
+ page as it progresses.</p>
+ </body>
+ </project>
+
+ <project cat='net'>
+ <title>SMP-Friendly pf(4)</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Gleb</given>
+ <common>Smirnoff</common>
+ </name>
+ <email>glebius at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url
+ href="http://svnweb.freebsd.org/base/projects/pf/head/">Project SVN branch</url>
+
+ <url
+ href="http://lists.freebsd.org/pipermail/freebsd-pf/2012-June/006643.html">Alpha announcement email thread</url>
+ </links>
+
+ <body>
+ <p>The project is aimed at moving the <tt>pf(4)</tt> packet filter
+ out of single mutex, as well as in general improving of its &os;
+ port.</p>
+
+ <p>The project is near its finish, the code is planned to go into
+ head after more testing and benchmarking. If you are interested
+ in details, please see the corresponding email thread on
+ freebsd-pf (see links).</p>
+ </body>
+
+ <help>
+ <task>Rewrite the <tt>pf(4)</tt> <tt>ioctl()</tt> interface so
+ that it does not utilize in-kernel structures. That would make
+ ABI more stable and ease future development.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>Portbuilder</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>David</given>
+ <common>Naylor</common>
+ </name>
+ <email>naylor.b.david at gmail.com</email>
+ </person>
+ </contact>
+
+ <links>
+ <url
+ href="https://github.com/DragonSA/portbuilder">Git Repository</url>
+ <url
+ href="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/README">README</url>
+ <url
+ href="https://github.com/DragonSA/portbuilder/blob/0.1.5.2/TODO">TODO</url>
+ </links>
+
+ <body>
+ <p>Since the last update there has been 2 feature releases and 4
+ bug-fix releases. A highlight of the changes made:</p>
+
+ <ul>
+ <li>Support has been added for:</li>
+ <ul>
+ <li><tt>-j</tt>: controlling concurrency per stage</li>
+ <li>pkgng: next generation package manager</li>
+ <li>installing packages via repository</li>
+ <li>dynamic defaults (loaded from
+ <tt>/etc/make.conf</tt>)</li>
+ <li>new options framework (aka OptionsNG)</li>
+ </ul>
+
+ <li>Some of the fixes include:</li>
+ <ul>
+ <li>correct assertions</li>
+ <li>correct build logic</li>
+ <li>retry when kevent receives <tt>EINTR</tt></li>
+ <li>correctly detecting installed ports</li>
+ <li>many fixes in the build logic</li>
+ </ul>
+ </ul>
+
+ <p>A benchmark was run timing portbuilder against a standard ports
+ build of KDE (<tt>x11/kde4</tt>) in a clean <tt>chroot(8)</tt>
+ environment. Portbuilder achieved a build time of 2:21:16
+ compared to ports build time of 4:47:21 for an decreased build
+ time of 51% from using portbuilder.</p>
+ </body>
+ </project>
+
+ <project cat='team'>
+ <title>The &os; Port Management Team</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Thomas</given>
+ <common>Abthorpe</common>
+ </name>
+ <email>portmgr-secretary at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Port</given>
+ <common>Management Team</common>
+ </name>
+ <email>portmgr at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://www.FreeBSD.org/ports/" />
+ <url
+ href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" />
+ <url href="http://portsmon.freebsd.org/index.html" />
+ <url href="http://www.freebsd.org/portmgr/index.html" />
+ <url href="http://blogs.freebsdish.org/portmgr/" />
+ <url href="http://www.twitter.com/freebsd_portmgr/" />
+ <url href="http://www.facebook.com/portmgr" />
+ </links>
+
+ <body>
+ <p>The ports tree slowly approaches 24,000 ports. The PR count
+ still is close to 1200.</p>
+
+ <p>In Q2 we added 7 new committers and took in one commit bit for
+ safe keeping.</p>
+
+ <p>The Ports Management team have been running -exp runs on an
+ ongoing basis, verifying how base system updates may affect the
+ ports tree, as well as providing QA runs for major ports
+ updates. Of note, -exp runs were done for:</p>
+
+ <ul>
+ <li>automake update</li>
+ <li>cmake update</li>
+ <li>xorg update</li>
+ <li>png update</li>
+ <li>Fix make reinstall</li>
+ <li>Implement <tt>USE_QT4</tt> in <tt>bsd.ports.mk</tt></li>
+ <li>KDE4 update</li>
+ <li>XFCE4 update</li>
+ <li>bison update</li>
+ <li>perl5.14 as default</li>
+ <li>ruby1.9 as default</li>
+ <li>ruby1.8 update</li>
+ <li>bsdsort regression test</li>
+ </ul>
+
+ <p>A lot of focus during this period was put into getting the
+ ports tree into a ready state for &os; 9.1.</p>
+
+ <p>A significant step forward was the implementation of
+ OptionsNG.</p>
+
+ <p>A record number of Port Managers attended BSDCan 2012, with
+ five being present to partake in the week of events, culminating
+ in a portmgr PR closing session that dealt with 18 PRs in one
+ day. You can see a group photo at <a
+ href="http://www.facebook.com/portmgr"/>. While you are
+ there, please click on the "Like" icon.</p>
+
+ <p>Beat Gaetzi has been doing ongoing tests with the ports tree to
+ ensure a smooth transition from CVS to Subversion. The tree was
+ successfully migrated the weekend of June 14, 2012.</p>
+ </body>
+
+ <help>
+ <task>Looking for help getting <a
+ href="http://wiki.freebsd.org/PortsAndClang">ports to build with
+ clang</a>.</task>
+
+ <task>Looking for help fixing <a
+ href="http://wiki.freebsd.org/PortsFailingOnCurrent">ports
+ broken on CURRENT</a>. (List needs updating, too.)</task>
+
+ <task>Looking for help with <a
+ href="http://wiki.freebsd.org/PortsBrokenOnTier2Architectures">Tier-2
+ architectures</a>.</task>
+
+ <task><a
+ href="http://wiki.freebsd.org/PortsBrokenBySrcChanges">ports
+ broken by src changes</a>.</task>
+
+ <task><a
+ href="http://wiki.freebsd.org/PortsFailingOnPointyhat">ports
+ failing on pointyhat</a>.</task>
+
+ <task><a
+ href="http://wiki.freebsd.org/PortsFailingOnPointyhatWest">ports
+ failing on pointyhat-west</a>.</task>
+
+ <task><a href="http://wiki.freebsd.org/Trybroken">ports that are
+ marked as <tt>BROKEN</tt></a>.</task>
+
+ <task><a href="http://wiki.freebsd.org/WhenDidThatPortBreak">When
+ did that port break</a>?</task>
+
+ <task>Most ports PRs are assigned, we now need to focus on
+ testing, committing and closing.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>Redports</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Bernhard</given>
+ <common>Froehlich</common>
+ </name>
+ <email>decke at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://www.redports.org/"/>
+ </links>
+
+ <body>
+ <p>There was good progress in the last half a year and a lot of
+ support from different parties to make redports a stable and
+ fast service.</p>
+
+ <p>A long known security concern within tinderbox was raised at
+ the BSD-Day in Vienna which was addressed by beat. That
+ improves security and isolation of the concurrent running jobs a
+ lot and gives me peace of mind.</p>
+
+ <p>We also recently got two beefy machines from the &os;
+ Foundation which increases computing power a lot. So no more
+ backlogs and your jobs finish much quicker.</p>
+
+ <p>But as usual now that we have enough power I was able to make
+ another promise come true and integrated Ports QAT functionality
+ into redports. Ports QAT was an automated services that did a
+ buildtest after each commit to the official &os; ports tree. If
+ a build fails it sends out mails and logfiles to the committer.
+ That finds bad commits quickly and allows the committer to fix
+ it before the first user notices. The former service stopped
+ about 2 years ago and we had no proper replacement for that task
+ at hand. Now that this is fully integrated into redports it
+ also gives us all the nice benefits of a common platform.</p>
+ </body>
+
+ <help>
+ <task>Automatic build incoming patches from Ports PRs in redports
+ and send results to GNATS database.</task>
+
+ <task>People want an GCC testing environment on redports where all
+ ports are build with <tt>lang/gcc47</tt>. To make that happen
+ we need to patch the ports framework to handle that and
+ correctly bootstrap with base GCC. This also gives us the
+ possibility to build all our binary packages with a modern gcc
+ and is easy to use for regular users. Contributors?</task>
+ </help>
+ </project>
+
+ <project cat='bin'>
+ <title>Replacing the Regular Expression Code</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Gábor</given>
+ <common>Kövesdán</common>
+ </name>
+ <email>gabor at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://laurikari.net/tre/">TRE home page</url>
+ </links>
+
+ <body>
+ <p>It has been decided to implement the optimizations and
+ extensions as a more isolated layer and not directly in TRE
+ itself. Since the last report there has been some progress in
+ this direction and the code has been significantly refactored.
+ It does not work yet in this new form but it is close to a
+ working state. Apart from this, the multiple pattern matching
+ needs some debugging and some minor features are missing.</p>
+ </body>
+
+ <help>
+ <task>Finish multiple pattern heuristic regex matching.</task>
+ <task>Implement GNU-specific regex extensions.</task>
+ <task>Test performance, standard-compliance and correct
+ behavior.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>BSD-licensed Sort Utility (GNU sort(1) Replacement)</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Oleg</given>
+ <common>Moskalenko</common>
+ </name>
+ <email>oleg.moskalenko at citrix.com</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Gábor</given>
+ <common>Kövesdán</common>
+ </name>
+ <email>gabor at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url
+ href="http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/bsdsort/">&os; port of BSD sort(1)</url>
+ <url
+ href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sort.html">IEEE Std 1003.1-2008 sort(1) specification</url>
+ </links>
+
+ <body>
+ <p>BSD <tt>sort(1)</tt> has been made the default sort utility in
+ 10-CURRENT. It is compatible with the latest GNU
+ <tt>sort(1)</tt>, version 8.15, except that the multi-threaded
+ mode is not enabled by default.</p>
+ </body>
+
+ <help>
+ <task>When the track record of the BSD <tt>sort(1)</tt> allows,
+ remove GNU <tt>sort(1)</tt> from -CURRENT.</task>
+
+ <task>Improve reliability of the multi-threaded sort and
+ investigate the possibility of making it the default compilation
+ mode.</task>
+
+ <task>Investigate possibility of factoring out the sort
+ functionality into a standalone library so that other utilities
+ can also make use of it.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>Xorg on &os;</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Martin</given>
+ <common>Wilke</common>
+ </name>
+ <email>miwi at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Koop</given>
+ <common>Mast</common>
+ </name>
+ <email>kwm at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Niclas</given>
+ <common>Zeising</common>
+ </name>
+ <email>zeising at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Eitan</given>
+ <common>Adler</common>
+ </name>
+ <email>eadler at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://wiki.freebsd.org/Xorg"/>
+ <url href="http://trillian.chruetertee.ch/ports/browser/trunk"/>
+ </links>
+
+ <body>
+ <p>During the beginning of this period, an update to the xorg
+ distribution for &os; was made, dubbed xorg 7.5.2. This update
+ included a new flag, <tt>WITH_NEW_XORG</tt>, to get a more
+ recent xorg distribution for those with modern hardware. To get
+ KMS support for recent Intel graphics chipsets <tt>WITH_KMS</tt>
+ must also be set. This requires a recent &os; 10-CURRENT or
+ &os; 9-STABLE.</p>
+ </body>
+
+ <help>
+ <task>Switch to use FreeGLUT instead of libGLUT, since the latter
+ is old and has there is no upstream support or releases any
+ more. Work on this is mostly done.</task>
+
+ <task>Update the xorg distribution to what is in the development
+ repository. The xorg project recently did a new release, and
+ the development repository contains this release. It needs more
+ testing before it can be merged, and a CFT was sent out in the
+ beginning of June. Work on this is ongoing.</task>
+
+ <task>Decide how to handle the new and old xorg distributions. In
+ recent xorg, a lot of legacy driver support has been dropped,
+ therefore we need to maintain two xorg distributions to not
+ loose a lot of hardware drivers. Currently, this is done by
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list