meta-openembedded/meta-perl
wangmy 3459e017b8 libcrypt-openssl-rsa-perl: upgrade 0.32 -> 0.33
0001-Fix-for-Issue-31.patch
removed since it's included in 0.33

Changelog:
=========
- Update for windows github CI
- Remove duplicit 'LICENSE' key
- Remove EUMM Remove version check
- #31 by removing reference to RSA_SSLV23_PADDING (removed from OpenSSL starting from v3.0.0)
- support passphase protected private key load
- fix 'unsupported encryption' error on old library versions
- Clarify croak message for missing passphrase on older cyphers
- More structs opaqued in LibreSSL 3.5
- Use a macro for dealing with older SSL lacking macros
- more CI fixups. Drop testing for 5.10 and 5.8. Something is broken upstream.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit a97f771d35)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2023-03-29 16:20:46 -04:00
..
conf layer.conf: change layer priority to match oe-core 2022-02-28 08:39:26 -08:00
recipes-extended recipes: Update LICENSE variable to use SPDX license identifiers 2022-03-04 17:41:45 -08:00
recipes-perl libcrypt-openssl-rsa-perl: upgrade 0.32 -> 0.33 2023-03-29 16:20:46 -04:00
COPYING.MIT meta-perl creation 2013-08-16 12:58:29 +02:00
README meta-openemnedded: Add myself as kirkstone maintainer 2022-04-23 17:14:31 -07:00

meta-perl

This layer provides commonly-used perl related recipes such as perl libraries in the Comprehensive Perl Archive Network.

Contents and Help

In this section the contents of the layer is listed, along with a short help for each package.

     -- libdbi-perl --
     The DBI is a database access module for the Perl programming language.
     It defines a set of methods, variables, and conventions that provide
     a consistent database interface, independent of the actual database
     being used.
                  |<- Scope of DBI ->|
                       .-.   .--------------.   .-------------.
       .-------.       | |---| XYZ Driver   |---| XYZ Engine  |
       | Perl  |       | |   `--------------'   `-------------'
       | script|  |A|  |D|   .--------------.   .-------------.
       | using |--|P|--|B|---|Oracle Driver |---|Oracle Engine|
       | DBI   |  |I|  |I|   `--------------'   `-------------'
       | API   |       | |...
       |methods|       | |... Other drivers
       `-------'       | |...
                       `-'

    -- libdbd-sqlite-perl --
    DBD::SQLite is a Perl DBI driver for SQLite, that includes the entire
    thing in the distribution. So in order to get a fast transaction capable
    RDBMS working for your perl project you simply have to install this
    module, and nothing else.

    usage: there is a test case to show you how it works

    1) vim local.conf:
    ...
    IMAGE_INSTALL:append = " libdbd-sqlite-perl"
    PERL_DBM_TEST = "1"
    ...
    2) build core-image-sato and boot the target

    3) run "sqlite-perl-test.pl" on target. This script includes five
       operations create/insert/update/delete/select to do with a table.

    More information can be found in the recipe's git log.

Dependencies

This layer depends on:

URI: git://git.openembedded.org/openembedded-core branch: kirkstone

Adding the meta-perl layer to your build

In order to use this layer, you need to make the build system aware of it.

Assuming the meta-perl layer exists at the top-level of your yocto build tree, you can add it to the build system by adding the location of the meta-perl layer to bblayers.conf, along with any other layers needed. e.g.:

BBLAYERS ?= "
/path/to/oe-core/meta
/path/to/layer/meta-perl \

Maintenance

Send patches / pull requests to openembedded-devel@lists.openembedded.org with '[meta-perl][kirkstone]' in the subject.

When sending single patches, please using something like: git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-perl][kirkstone][PATCH'

Layer maintainers: Armin Kuster akuster808@gmail.com

License

All metadata is MIT licensed unless otherwise stated. Source code included in tree for individual recipes is under the LICENSE stated in each recipe (.bb file) unless otherwise stated.