The package dependency speedup was committed by portmgr, unfortunately it was not the latest version of it. The most recent version is scheduled for an experimental ports build run (my patch also contains the possibility to switch of the registration of implicit dependencies, if enabled it gives a much better picture regarding which port needs to be rebuild (portrevision bump) in case a dependency changes).
Patches for speeding up “make clean” are also scheduled for an experimental ports build run. The pkg_create patch was also committed to -current.
With all those stuff an update is much faster now, at least for those ports where the compile/build time was much lower than the infrastructure processing (I doubt you will see a significant change in a build of OO 😉 ).
Stephen Montgomery-Smith posted some patches for bsd.port.mk to the ports mailinglist to speed up the package dependency list creation. He did cut down the time from about 2min30sec (package dependency list of gnome2, tested on my system) to about 15 – 18sec. I enhanced this and now the time is down to about 12sec and a lot less programs to execute in the call (may be important on slow systems).
The patch for bsd.port.mk in my ports-patches directory contains more than only those improvements, the other part is not subject to submission yet.
If nobody finds some problems with the patch I will send it to GNATS and assign it to portmgr for inclusion into one of the next experimental ports builds.
The last week has seen some bikesheds. One of them was my commit of the doxygen infrastructure for the kernel subsystems. Some people don’t like the way doxygen requires some markup tags in the comments, some people don’t think such API docs provide additional value and some people fear that 3rd party developers may use some functions which shouldn’t be used. I don’t repeat the counter-arguments of myself and other people here, but there are people out there which already make use of the current unsatisfactory doxygen output and are happy about this infrastructure. Luckily is was superseeded by another bikeshed (and gnn@ wants to work on documenting a subsystem to show the benefits to those people which do not think yet, that this is a good idea). On a related issue, I’m waiting on a repo copy of src/sys/doc to src/tools (it’s one of two repo copies I’m waiting for, ncvs@ seems to be bussy ATM). Some doc@ people think it is more appropriate there.
The FC4 linux base port and the xorg based linux X11 libs port are scheduled for testing in an experimental ports build run, we may see the switch of the default linux base port in the not so distant future. It seems Boris is working on updates to the rest of the linuxolator infrastructure in the Ports Collection (gtk, …), so we may see a lot of updates there after the switch of the default linux base port.
In the last days I also helped/talked with my SoC students. Roman is playing a little bit with an amd64 tinderbox he got access to and as a result he committed support for building the linuxolator on amd64 as a module to perforce (call for testers: he did send a patch to emulation@, please give it a try if you own an amd64 box). Ryan is cataloging the IOCTL’s and their status (implemented, obsolete, …) in the FreeBSD wiki. I already priorized those he did so far, and gave some suggestions how to proceed with the important ones. This way he hasn’t to wait for me or Ariff when he is finished with the cataloging (being a mentor living in a different time zone means you should be ahead of your student… being ahead even before he is able to asks questions is … a boost for your own ego 😉 ).