Category Archives: Team

[CFT] Xorg 7.7 ready for testing!

Hi Fans,

The FreeBSD Xorg Team is pleased to announce Xorg 7.7 Release. We are very happy to be able to Call for testing shortly after the Xorg team annouced 7.7 release. This CFT is also open for discussion on how we should move forward with xorg release as we are facing some issues and we would like to ask for your opinion. Right now we have 2 existing xorg versions in our Ports Tree. The situation is quite bad due to our poor graphic card support. That means we do not have much choice but to take it as how it is now. But with regards to mesa support, we have to face some new challanges.

With the new mesa 8.0 release, accelerated support for a number of older graphic cards was dropped. At the moment we are not sure how to deal with that.We are thinking of just replacing mesa 7.11 with 8.0 or making a new flag like WITH_MESA= 7.11.2 / 8.0 in combination with WITH_NEW_XORG, and let the mesa 7.6.1 set as default together with the old xorg version. Obviosly the latter option make the already complex situation more complex. The problem is, users, especially  the new ones can easily get confused with it. Another issue is, the packages.We can’t deliver a package set with the new Xorg releases. This means users with new hardware will have to compile everything by themselves. Though I’m totally fine with compiling, not everyone has the CPU power to compile everything. What I’m trying to say is, I would love to see the newer xorg released as the default version, but i know this will break a lot of old hardware. The thing is, when we want to try to become a Modern Operating System, I dont see any other way to make the new xorg as default but to give Users the chance to compile the old xorg with a flag like WITH_OLD_XORG.

Some notes regarding KMS support:
KMS Support has been completely migrated to FreeBSD 10. The MFC to 9 will come soon, that means so long its not MFC’d to 9-Stable, users need to get the latest patch from our x11 mailing list.

This testing includes
* libdrm 2.4.34 (including KMS support)
* mesa 8.0.3
* full Xorg 7.7 release

Checkout Xorg Development Repo:
You will need to install devel/subversion in order to checkout the xorg repo. Next, you will need to add WITH_NEW_XORG=yes in your /etc/make.conf if you want to try out the new Xorg and mesa. Note
that if you are not qualified for the KMS patch, you shouldn’t use WITH_NEW_XORG=yes because the old intel driver doesn’t build with the new X server. If you are qualified, you should also set WITH_KMS=yes
in /etc/make.conf. Nvidia and ATI users should set WITH_NEW_XORG=yes.

svn co https://trillian.chruetertee.ch/svn/ports/trunk

A small merge script to merge the svn checkout into the real portstree can be found here:

http://people.freebsd.org/~miwi/xorg/xorgmerge

The script is a modified version of the old kdemerge script. Please set the KDEDIR variable to the path of your X.org ports. After merging, run one of the following command, depending on which
tool you use to manage your installed packages.

portupgrade -af \*
portmaster -a

After installing these, you will have to rebuild all xf86-* ports. We will bump all releated ports during the commit to the ports tree.

Roadmap:
Our current plan is to let the CFT running for a while, and see what the outcome of the discussion above is. We hope to get a lot of feedback to solve as many problems as possible. Also we are working on the
libglut to freeglut migration, this will definitely complete before we import Xorg 7.7. So we still have enough time.  We are looking forward for your feedback.

– miwi on behalf of the FreeBSD X11 Team

[CFT] VirtualBox 4.0.4 for FreeBSD

Time for a new round FreeBSD Vbox’s Team called for Testing,

A few of you have probably wondered what happened to our VirtualBox
efforts for FreeBSD. Well it took a bit longer then expected and a few
problems were found that needed to be resolved first but most of the
things are looking fine now and almost all patches have been pushed
upstream with 4.0.4 so here we are now.

We will continue to work on VirtualBox for FreeBSD and upstream is also
very helpful to us but we could need a few more hands to better keep up
with the work and especially improve and fix the Guest Additions. So if
you want to help please contact us or have a look at our Todo list.

This result wouldn’t have been possible without the continuous help of
the VirtualBox Developers and a lot of people from the FreeBSD
community! (names in alphabetical order and probably missed a few,
sorry
for that!)

- Alexander Eichner
- Anonymous
- Beat Gätzi
- Bernhard Fröhlich
- crsd
- DomiX
- Doug Barton
- Grzegorz Blach
- Hans Petter Selasky
- Julian Stacey
- Jung-uk Kim
- Jürgen Lock
- Klaus Espenlaub
- Martin Wilke
- Mattia Rossi
- Michael Butler
- Sean C. Farley
- Steve Wills
- tombsd
- Vivek Khera
- well-wisher
- Wietse Venema
- Yuri
- many more from emulation@

Please when testing this ports backup all your virtual machines first.
Also please build the port with DEBUG option enabled and send us the
logfile when any VM crashes. Without them it’s very hard to figure out
what went wrong.

Highlights with 4.0:
- USB support (by Hans Petter Selasky)
- Asynchronous I/O
- Guest additions got startscripts and a integration into the desktop
environments
- www/phpvirtualbox updated to 4.0-3

Changelog for 4.0:
- http://www.virtualbox.org/wiki/Changelog

Short configuration help:
- http://wiki.freebsd.org/VirtualBox

Todo List:
- http://wiki.freebsd.org/VirtualBox/ToDo

http://home.bluelife.at/ports/virtualbox-cft-20110218.tar.gz


Thanks and good luck,

Python Infrastructure changes Roadmap

Howdy,

I just want to inform you that the python team plans to make some infrastructure changes.
The changes involves the following 3 steps:

[python 2.5/2.6/2.7 improvements/ py 3.2 adding]
We plan to integrate some important patches:
ports/153952 ports/148406 ports/149167 ports/152224 ports/133081

python 3.2 will be released on 12 Feb, we’ll wait for the final release
before adding it to the build. For all of these we will do an exp-run
to make sure nothing will break during the build. It takes approximately 2 weeks if all works fine.

[python24 removal]
Python 2.4 is not supported anymore since 2008, and it has a lot of security problems.
Unfortunately this will cause the removal of some zope stuff. The following ports are affected:

www/zope210
www/zope211
www/zope28
www/zope29
+ zope plugins which are dependant on one of these ports. Philip is working on an
update to some new zope versions. I hope we can cooperate with him to get things
smoothly done. For all these we will do an exp-run to make sure nothing will break during
build. It takes approximately 3 weeks if all works fine.

[python 2.7 move to default]
python 2.7 is already stable enough to be moved over as default. For this one we will do an exp-run
to make sure nothing will break during the build. If all works fine, we think we can complete it by the
first week of March.