| flex |
2.6.4 |
Flex (The Fast Lexical Analyzer) |
openembedded-core |
| flexbe-behavior-engine |
1.3.1-1 |
A meta-package to aggregate all the FlexBE packages |
meta-ros1-melodic |
| flexbe-behavior-engine |
|
|
meta-ros1-noetic |
| flexbe-core |
1.3.1-1 |
flexbe_core provides the core components for the FlexBE behavior engine. |
meta-ros1-melodic |
| flexbe-core |
|
|
meta-ros1-noetic |
| flexbe-input |
1.3.1-1 |
flexbe_input enables to send data to onboard behavior when required. |
meta-ros1-melodic |
| flexbe-input |
|
|
meta-ros1-noetic |
| flexbe-mirror |
1.3.1-1 |
flexbe_mirror implements functionality to remotely mirror an executed behavior. |
meta-ros1-melodic |
| flexbe-mirror |
|
|
meta-ros1-noetic |
| flexbe-msgs |
1.3.1-1 |
flexbe_msgs provides the messages used by FlexBE. |
meta-ros1-melodic |
| flexbe-msgs |
|
|
meta-ros1-noetic |
| flexbe-onboard |
1.3.1-1 |
flexbe_onboard implements the robot-side of the behavior engine from where all behaviors are started. |
meta-ros1-melodic |
| flexbe-onboard |
|
|
meta-ros1-noetic |
| flexbe-states |
1.3.1-1 |
flexbe_states provides a collection of predefined states. Feel free to add new states. |
meta-ros1-melodic |
| flexbe-states |
|
|
meta-ros1-noetic |
| flexbe-testing |
1.3.1-1 |
flexbe_testing provides a framework for unit testing states. |
meta-ros1-melodic |
| flexbe-testing |
|
|
meta-ros1-noetic |
| flexbe-widget |
1.3.1-1 |
flexbe_widget implements some smaller scripts for the behavior engine. |
meta-ros1-melodic |
| flexbe-widget |
|
|
meta-ros1-noetic |
| libreflexxestype2 |
0.8.8-1 |
Package with ReflexxesTypeII implementation and header files |
meta-ros1-melodic |
| move-base-flex |
0.4.0-1 |
Move Base Flex (MBF) is a backwards-compatible replacement for move_base. MBF can use existing plugins for move_base, and provides an enhanced version of the planner, controller and recovery plugin ROS interfaces. It exposes action servers for planning, controlling and recovering, providing detailed information of the current state and the plugin’s feedback. An external executive logic can use MBF and its actions to perform smart and flexible navigation strategies. Furthermore, MBF enables the use of other map representations, e.g. meshes or grid_map This package is a meta package and refers to the Move Base Flex stack packages.The abstract core of MBF – without any binding to a map representation – is represented by the <a href="http://wiki.ros.org/mbf_abstract_nav">mbf_abstract_nav</a> and the <a href="http://wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. For navigation on costmaps see <a href="http://wiki.ros.org/mbf_costmap_nav">mbf_costmap_nav</a> and <a href="http://wiki.ros.org/mbf_costmap_core">mbf_costmap_core</a>. |
meta-ros1-melodic |
| move-base-flex |
|
|
meta-ros1-noetic |
| ros-reflexxesblacklisted |
0.8.8-1 |
The ros_reflexxes package |
meta-ros1-melodic |
| acpid |
2.0.32 |
A daemon for delivering ACPI events |
openembedded-core |
| dancer2-plugin-auth-yarbac-perl |
0.009 |
YARBAC is a role based user authentication and authorisation framework for Dancer2 apps. Designed with security and a medium to large user base in mind. This framework was heavily inspired by the excellent Dancer::Plugin::Auth::Extensible framework which I'd highly recommend. YARBAC was designed to support secure password checking, enforced password hashing, multiple authentication realms and the ability to create your own backend provider. YARBAC was also designed to to be as flexible and as feature rich as possible in the hope that I'll never have to write RBAC code for Dancer again. :) While similar to Extensible in some ways, this framework has some significantly different approaches. These differences were born out of my own experiences writing RBAC code for various Dancer apps and finding myself always having to extend existing modules or starting from scratch or worse still, copy/paste my old code then reworking it. The major difference with YARBAC is that it tries to be a complete solution to the problem. However in order to be a little more flexible and feature rich in some areas it is also a little more opinionated in others. The main area of opinion in YARBAC is how it achieves role-based access control. YARBAC is structed with users, roles, groups and permissions. A user can have many roles but it might be a good idea in larger enviornments to only allow a user to have one role and then assign that role have many groups. Think of a role as being a role-group. Then there are groups which have many permissions. A user can have one or more roles, a role can have one or more groups and groups can have one or more permissions. This means when deciding if a user is authorised we could require they be logged in, or have a specifc role, or specific group, or a specific group with a specific permission and so on. To put it another way, this design moves the access control down to the role-group relationship thus allowing one to quickly and easily see, assign or revoke permissions to a user even when dealing with a fairly complex authorisation environment. |
meta-cpan |
| dante |
1.4.1 |
A free SOCKS server |
meta-networking |
| dom4j |
1.6.1 |
A simple and flexible library for working with XML, XPath and XSLT |
meta-java |
| dstat |
0.7.4 |
versatile resource statics tool |
meta-oe |
| go |
1.15.8 |
Go programming language compiler |
openembedded-core |
| go-cross-canadian-i686 |
1.15.8 |
Go programming language compiler |
openembedded-core |
| go-cross-core2-32 |
1.15.8 |
Go programming language compiler |
openembedded-core |
| go-crosssdk-x86_64-oesdk-linux |
1.15.8 |
Go programming language compiler |
openembedded-core |
| go-native |
1.15.8 |
Go programming language compiler |
openembedded-core |
| go-runtime |
1.15.8 |
Go programming language compiler |
openembedded-core |
| grub |
2.04 |
GRUB2 is the next-generation GRand Unified Bootloader |
openembedded-core |
| grub |
0.97 |
GRUB is the GRand Unified Bootloader |
meta-gplv2 |
| grub-efi |
2.04 |
GRUB2 is the next-generation GRand Unified Bootloader |
openembedded-core |
| gupnp |
1.2.4 |
UPnP framework |
meta-multimedia |
| ipr-externblacklisted |
0.8.8-1 |
Package with external libraries used in Industrial and Service workspaces. Currentlly supported Libraries: Reflexxes, Libmodbus. |
meta-ros1-melodic |
| jq |
1.6 |
Lightweight and flexible command-line JSON processor |
meta-oe |
| kernel-module-imx-gpu-viv |
6.4.3.p1.0 |
Kernel loadable module for Vivante GPU |
meta-freescale |
| liblogging |
1.0.6 |
An easy to use logging library |
meta-oe |
| libpam |
1.3.1 |
Linux-PAM (Pluggable Authentication Modules) |
openembedded-core |
| libtest-deep-perl |
1.130 |
Test::Deep - Extremely flexible deep comparison |
meta-perl |
| log-any-adapter-daemontools-perl |
0.102 |
In the daemontools way of thinking, a daemon writes all its logging output to STDOUT (or STDERR), which is a pipe to a logger process. Doing this instead of other logging alternatives keeps your program simple and allows you to capture errors generated by deeper libraries (like libc) which aren't aware of your logging API. If you want complicated logging you can keep those details in the logging process and not bloat each daemon you write. This module aims to be the easiest, simplest, most efficent way to get Log::Any messages to a file handle while still being flexible enough for the needs of the typical unix daemon or utility script. |
meta-cpan |
| log4c |
1.2.4 |
Log4c is a C library for flexible logging to files, syslog and other destinations |
meta-oe |
| log4cpp |
1.1.3 |
A library of C++ classes for flexible logging to files, syslog, IDSA and other destinations. |
meta-oe |
| mbedtls |
2.1.1 |
An open source, portable, easy to use, readable and flexible SSL library |
meta-digi-dey |
| mbf-abstract-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros1-melodic |
| mbf-abstract-nav |
0.4.0-1 |
The mbf_abstract_nav package contains the abstract navigation server implementation of Move Base Flex (MBF). The abstract navigation server is not bound to any map representation. It provides the actions for planning, controlling and recovering. MBF loads all defined plugins at the program start. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. |
meta-ros1-melodic |