| 4th-gen-i5-i7-sinit |
75 |
ACM for Intel Haswell (HSW) machines |
meta-measured |
| 5th-gen-i5-i7-sinit |
79 |
ACM for Intel Broadwell machines |
meta-measured |
| aircrack-ng |
1.2 |
Aircrack-ng is a set of tools for auditing wireless networks |
meta-security |
| antlr |
2.7.7 |
Framework for constructing recognizers, interpreters, compilers, and translators |
meta-java |
| arm-trusted-firmware |
1.5+gitX |
ARM Trusted Firmware |
meta-ti |
| atmel-xplained-lcd-demo-image |
1.0 |
An image for boards with screen and resistive touchscreen. |
meta-atmel |
| audiofile |
0.3.6 |
The Audio File Library provides a uniform and elegant API for accessing a variety of audio file formats, such as AIFF/AIFF-C, WAVE, NeXT/Sun .snd/.au, Berkeley/IRCAM/CARL Sound File, Audio Visual Research, Amiga IFF/8SVX, and NIST SPHERE. |
meta-oe |
| autoconf |
2.69 |
A GNU tool that produce shell scripts to automatically configure software |
openembedded-core |
| baloo |
5.44.0 |
Baloo provides searching and indexing infrastucture with an emphasis on files |
meta-qt5-extra |
| base-files |
3.0.14 |
Miscellaneous files for the base system |
openembedded-core |
| binutils |
2.29.1 |
GNU binary utilities |
openembedded-core |
| binutils |
linaro-2.27 |
GNU binary utilities |
meta-linaro-toolchain |
| binutils |
linaro-2.25 |
GNU binary utilities |
meta-linaro-toolchain |
| binutils-cross-canadian-i586 |
2.29.1 |
GNU binary utilities (cross-canadian for i586 target) |
openembedded-core |
| binutils-cross-canadian-i586 |
linaro-2.25 |
GNU binary utilities (cross-canadian for i586 target) |
meta-linaro-toolchain |
| binutils-cross-canadian-i586 |
linaro-2.27 |
GNU binary utilities (cross-canadian for i586 target) |
meta-linaro-toolchain |
| binutils-cross-i586 |
2.29.1 |
GNU binary utilities |
openembedded-core |
| binutils-cross-i586 |
linaro-2.27 |
GNU binary utilities |
meta-linaro-toolchain |
| binutils-cross-i586 |
linaro-2.25 |
GNU binary utilities |
meta-linaro-toolchain |
| binutils-crosssdk-x86_64-oesdk-linux |
2.29.1 |
GNU binary utilities |
openembedded-core |
| binutils-crosssdk-x86_64-oesdk-linux |
linaro-2.27 |
GNU binary utilities |
meta-linaro-toolchain |
| binutils-crosssdk-x86_64-oesdk-linux |
linaro-2.25 |
GNU binary utilities |
meta-linaro-toolchain |
| bitflags |
0.8.2 |
A macro to generate structures which behave like bitflags. |
meta-rust |
| boinc-client |
7.6.33 |
Open-source software for volunteer computing |
meta-oe |
| breakpad |
1.0+gitX |
An open-source multi-platform crash reporting system |
meta-oe |
| busybox |
1.24.1 |
Tiny versions of many common UNIX utilities in a single small executable |
openembedded-core |
| busybox |
1.30.1 |
Tiny versions of many common UNIX utilities in a single small executable |
meta-tanowrt |
| busybox-initramfs |
1.24.1 |
Tiny versions of many common UNIX utilities in a single small executable |
meta-ampliphy |
| cairo |
1.14.10 |
The Cairo 2D vector graphics library |
openembedded-core |
| calibrateproto |
0.0+gitX |
XCalibrate: Touchscreen calibration headers |
openembedded-core |
| cfengine |
3.9.0 |
CFEngine is an IT infrastructure automation framework |
meta-oe |
| cfengine-masterfiles |
3.9.0 |
Base policy for CFEngine |
meta-oe |
| cgi-deurl-xs-perl |
0.08 |
This module decodes a URL-encoded parameter string in the manner of CGI.pm. However, as it uses C code from libapreq to perform the task, it's somewhere from slightly to much faster (depending on your strings) than using CGI or a functionally similar module like CGI::Deurl. |
meta-cpan |
| chrony |
2.4 |
Versatile implementation of the Network Time Protocol |
meta-networking |
| cinematicexperience |
1.0 |
Qt5 technology demo |
meta-qt5 |
| class-tiny-perl |
1.006 |
This module offers a minimalist class construction kit in around 120 lines of code. Here is a list of features: |
meta-cpan |
| class-xsaccessor-perl |
1.19 |
Class::XSAccessor implements fast read, write and read/write accessors in XS. Additionally, it can provide predicates such as "has_foo()" for testing whether the attribute "foo" exists in the object (which is different from "is defined within the object"). It only works with objects that are implemented as ordinary hashes. Class::XSAccessor::Array implements the same interface for objects that use arrays for their internal representation. |
meta-cpan |
| commons-codec |
1.3 |
Java library with simple encoder and decoders for various formats such as Base64 and Hexadecimal |
meta-java |
| concurrencykit |
0.5.1+gitX |
Concurrency Kit provides a plethora of concurrency primitives, safe memory reclamation mechanisms and non-blocking data structures designed to aid in the design and implementation of high performance concurrent systems. |
meta-oe |
| containerd-docker |
v0.2.x+git3addd840653146c90a254301d6c3a663c7fd6429 |
containerd is a daemon to control runC |
meta-virtualization |
| containerd-opencontainers |
0.2.2+git0ac3cd1be170d180b2baed755e8f0da547ceb267 |
containerd is a daemon to control runC |
meta-virtualization |
| convert-color-perl |
0.11 |
This module provides conversions between commonly used ways to express colors. It provides conversions between color spaces such as RGB and HSV, and it provides ways to look up colors by a name. |
meta-cpan |
| core-image-tiny-initramfs |
1.0 |
Tiny image capable of booting a device. The kernel includes the Minimal RAM-based Initial Root Filesystem (initramfs), which finds the first 'init' program more efficiently. core-image-tiny-initramfs doesn't actually generate an image but rather generates boot and rootfs artifacts that can subsequently be picked up by external image generation tools such as wic. |
openembedded-core |
| cpanel-json-xs-perl |
4.02 |
This module converts Perl data structures to JSON and vice versa. Its primary goal is to be *correct* and its secondary goal is to be *fast*. To reach the latter goal it was written in C. |
meta-cpan |
| crypt-cbc-perl |
2.33 |
This module is a Perl-only implementation of the cryptographic cipher block chaining mode (CBC). In combination with a block cipher such as DES or IDEA, you can encrypt and decrypt messages of arbitrarily long length. The encrypted messages are compatible with the encryption format used by the OpenSSL package. |
meta-cpan |
| crypt-ripemd160-perl |
0.06 |
The Crypt::RIPEMD160 module allows you to use the RIPEMD160 Message Digest algorithm from within Perl programs. The module is based on the implementation from Antoon Bosselaers from Katholieke Universiteit Leuven. A new RIPEMD160 context object is created with the new operation. Multiple simultaneous digest contexts can be maintained, if desired. The context is updated with the add operation which adds the strings contained in the *LIST* parameter. Note, however, that \"add('foo', 'bar')\", \"add('foo')\" followed by \"add('bar')\" and \"add('foobar')\" should all give the same result. The final message digest value is returned by the digest operation as a 20-byte binary string. This operation delivers the result of add operations since the last new or reset operation. Note that the digest operation is effectively a destructive, read-once operation. Once it has been performed, the context must be reset before being used to calculate another digest value. Several convenience functions are also provided. The addfile operation takes an open file-handle and reads it until end-of file in 8192 byte blocks adding the contents to the context. The file-handle can either be specified by name or passed as a type-glob reference, as shown in the examples below. The hexdigest operation calls digest and returns the result as a printable string of hexdecimal digits. This is exactly the same operation as performed by the unpack operation in the examples below. The hash operation can act as either a static member function (ie you invoke it on the RIPEMD160 class as in the synopsis above) or as a normal virtual function. In both cases it performs the complete RIPEMD160 cycle (reset, add, digest) on the supplied scalar value. This is convenient for handling small quantities of data. When invoked on the class a temporary context is created. When invoked through an already created context object, this context is used. The latter form is slightly more efficient. The hexhash operation is analogous to hexdigest. |
meta-cpan |
| ctapi-common |
1.1-14 |
Common files and packaging infrastructure for CT-API modules |
meta-oe |
| curaengine |
15.04.06 |
CuraEngine is a powerful, fast and robust engine for processing 3D models into 3D printing instructions. |
meta-maker |
| curaengine |
15.06.03 |
CuraEngine is a powerful, fast and robust engine for processing 3D models into 3D printing instructions. |
meta-maker |
| 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 |