the keyboard work automatically. It uses PulseAudio for chosing which
card/sink/track to act on.
This is a fork of the original xfce4-volumed to drop GStreamer support
and use PulseAudio instead.
WWW: https://launchpad.net/xfce4-volumed-pulse
Obtained from: Xfce dev repository
graphics/dri:
Move gettext:build to bsd.mesalib.mk so it present for all mesa ports. [1]
VDPAU needs GALLIUM so check for that, since it a Gallium state tracker. [1][2]
Rework llvm33/llvm34 selection so we can use the llvm version later on.
VDPAU links against the llvm libraries so we need to depend on the llvm port
as a run dependency .[1]
After discussion remove the VDPAU option for now. Radeon kernel drivers currently
don't support hardware-assisted video decoding. And Gallium/VDPAU doesn't support
the intel driver.
PR: 194655 [1]
PR: 194580 [2]
designed to be secure and auditable. See a Comparison of CGI Libraries in C for
alternatives. To start, download kcgi.tgz and run make install into your PREFIX
of choice. The kcgi(3) manpage documents usage. kcgi is a BSD.lv project
WWW: http://kristaps.bsd.lv/kcgi/
PORTVERSION of the speedtest-mini port is not correct.
2.2.0 is a swfobject library's version, not the version
of the speedtest-mini itself. IWAO-san found that an actual
version is probably 2.1.8 in index-php.html.
In addition, with consideration for the frequently-updated
of the speedtest-mini without explicit version incrementation,
he added distfile's timestamp into PORTVERSION. Thanks
PR: 195201
Submitted by: Koichiro IWAO
When the system first boots, resize the (GPT) partition holding the root
filesystem, then resize the (UFS) root filesystem. This is intended to be
used in virtual machines where a VM image is built with one size but may
be launched onto a larger disk.
This will be used in EC2 images in the near future.
- Introduce GNUTLS OPTION and make it default
- Add extra patch for gnutls support from mplayer svn head
While on it
- Fix cflags/ldflags in mencoder: USES pkgconfig
Dancer2::Plugin::Passphrase manages the hashing of passwords for
Dancer apps, allowing developers to follow cryptography best practices
without having to become a cryptography expert. It uses the bcrypt
algorithm as the default, while also supporting any hashing function
provided by Digest.
WWW: http://search.cpan.org/dist/Dancer2-Plugin-Passphrase/
PR: 194962
Submitted by: Henk van Oers <hvo.pm@xs4all.nl>
A user authentication and authorisation framework plugin for Dancer2 apps.
Makes it easy to require a user to be logged in to access certain
routes, provides role-based access control, and supports various
authentication methods/sources (config file, database, Unix system
users, etc).
Designed to support multiple authentication realms and to be as
extensible as possible, and to make secure password handling easy (the
base class for auth providers makes handling `RFC2307'-style hashed
passwords really simple, so you have no excuse for storing plain-text
passwords).
WWW: http://search.cpan.org/dist/Dancer2-Plugin-Auth-Extensible/
PR: 194961
Submitted by: Henk van Oers <hvo.pm@xs4all.nl>
Dancer2::Plugin::Database provides an easy way to obtain a connected
DBI database handle by simply calling the database keyword
within your Dancer2 application.
Returns a Dancer2::Plugin::Database::Handle object, which is a subclass of DBI's
DBI::db connection handle object, so it does everything you'd expect to do with
DBI, but also adds a few convenience methods. See the documentation for
Dancer2::Plugin::Database::Handle for full details of those.
WWW: http://search.cpan.org/dist/Dancer2-Plugin-Database/
PR: 194960
Submitted by: Henk van Oers <hvo.pm@xs4all.nl>
That is an example plugin that is not supposed to be built and installed by
default. Its sole purpose is to be an example of how to write a plugin, and
it does so by making <select> elements show up in a separate dialog. We
definitely do not want that. As a bonus, it allows us to remove some of the
hacks we do in the pre-configure target.
While here:
- Improve the comment about why we change ALL_TARGET.
- Remove the weird CONFIGURE_ENV change we did that does not seem to be
necessary anymore. I could not find any explanation for why it was added
in the first place.
