very basic browser whose feature list includes things like "History"
and "Bookmarks". It does not have support for netscape plugins, so
no flash support until Qt 4.5. But it is small, less than 10,000
lines of code, very fast, lean, mean and loads of fun to hack on.
Arora and QtWebKit is developed to be cross-platform using the Qt
library. It was originally created as a demo for Qt to help test
the QtWebKit component and find API issues and bugs before the
release.
WWW: http://code.google.com/p/arora/
Submitted by: Andy Fawcett <andy at athame.co.uk>
for FreeBSD. The official KDE 4.1.0 release notes can be found at
http://www.kde.org/announcements/4.1/.
Some note:
* Prefix
KDE4 will be install into a custom prefixes namely ${LOCALBASE}/kde4.
KDE4 and KDE3 can co-exist
* Sound
For sound to work, it is necessary to have dbus and hal enabled
in your system. Please see the respective documentation on how
to enable these.
For more Informations see the HEADS UP at ports@ and kde-freebsd@
or our wiki page http://wiki.freebsd.org/KDE4/Install.
Have fun!
It was created because of an article/challenge in "The Perl Review"
WWW: http://search.cpan.org/dist/Math-Base36/
PR: ports/126383
Submitted by: Yi-Hsuan Hsin <mhsin at mhsin.org>
o Update maintainer email address
Version 0.1.7 contains both bug fixes and new features compared to
0.1.6, most notably:
o UTF-8 support, finally non ASCII characters should render ok.
o RandR support, multi-screen configuration is now detected and should
be handled correctly.
o Viewport support removed, it was buggy and not used by many.
For a somewhat more complete list of changes see:
http://www.pekwm.org/projects/pekwm/wikis/Release-0_1_7
PR: 126318
Submitted by: Martin Tournoij <carpetsmoker@xs4all.nl> (maintainer)
list : lists available builds
clone : creates a new build by cloning a previous one
portsupdate : update a ports tree to the latest ZFS snapshot
srcupdate : update a src tree to the latest ZFS snapshot
cleanup : clean up or remove a build on the clients
destroy : remove a build on the server
There is some trickiness here in that various commands either expect
to run as root, or expect to run as a ports-* user. For the latter
case we can easily use su to proxy as the ports user when running as
root; for the former we use the buildproxy to validate and re-execute
the command as root.
