Mercurial repositories using SSH public key authentication; it provides
convenient and fine-grained key management and access control.
All of the repositories controlled by mercurial-server are owned by a single
user (the "hg" user in what follows), but many remote users can act on them,
and different users can have different permissions. We don't use file
permissions to achieve that - instead, developers log in as the "hg" user
when they connect to the repository host using SSH, using SSH URLs of the
form "ssh://hg@repository-host/repository-name". A restricted shell prevents
them from using this access for unauthorized purposes. Developers
are authenticated only using SSH keys; no other form of authentication is
supported.
To give a user access to the repository, place their key in an
appropriately-named subdirectory of "/usr/lcoal/etc/mercurialserver/keys"
and run "refresh-auth". You can then control what access they have to what
repositories by editing the control file
"/usr/local/etc/mercurialserver/access.conf", which can match the names of
these keys against a glob pattern.
For convenient remote control of access, you can instead (if you have the
privileges) make changes to a special repository called "hgadmin", which
contains its own "access.conf" file and "keys" directory. Changes pushed to
this repository take effect immediately. The two "access.conf" files are
concatenated, and the keys directories merged.
WWW: http://www.lshift.net/mercurial-server.html
PR: ports/151993
Submitted by: Aldis Berjoza <aldis at bsdroot.lv>
application.
It has builtin support for date formatting with timezone support as well as a
very simple and friendly interface to gettext translations.
WWW: http://pypi.python.org/pypi/Flask-Babel
PR: ports/151627
Submitted by: Olivier Duchateau <duchateau.olivier at gmail.com>
ELF assembler directives on PPC64 systems. As a result, it is not possible
to have functions named things like 'text' and 'data'.
In glib-compile-schemas.c we have such a name.
PR: ports/152555
Submitted by: andreast@
handle is "attached" to the circular relationship, but is not a part
of it. When the destroy handle falls out of scope, it will be cleaned
up correctly, and while being cleaned up, it will also force the data
structure it is attached to to be destroyed as well. Object::Destroyer
can call a specified release method on an object (or method DESTROY by
default). Alternatively, it can execute an arbitrary user code passed
to constructor as a code reference.
WWW: http://search.cpan.org/dist/Object-Destroyer/
PR: ports/152276
Submitted by: Gea-Suan Lin <gslin at gslin.org>
These includes messages for actions (actionlib_msgs), diagnostics
(diagnostic_msgs), geometric primitives (geometry_msgs), robot navigation
(nav_msgs), and common sensors (sensor_msgs), such as laser range finders,
cameras, point clouds.
WWW: http://www.ros.org/wiki/common_msgs
