# packages

name: perl-clobber
arch: src
version: 0.04
epoch: 0
release: 2.56
summary: Pragma to Optionally Prevent Over-Writing Files
url: http://search.cpan.org/dist/clobber/
rpm_license: GPL-1.0+ or Artistic-1.0
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb51
location_href: src/perl-clobber-0.04-2.56.src.rpm
checksum_type: sha512
pkgId:
  a07488e3d87c3f2ef53df297f56fa6ea587a3b8753738b48f27ef770f19465e2d90f8267e09f4d536f850c99c6f39e99c789e319be680e466fc07b4d5fe81c87

description:
  Do you occasionally get '+>' and '+<' mixed up, or accidentally leave off
  an > in the mode of an 'open'? Want to run some relatively trustworthy
  code--such as some spaghetti monster you created in the days of yore--but
  can't be bothered to check it's semantics? Or perhaps you'd like to add a
  level of protection to operations on user-supplied files without coding the
  logic yourself.

  Yes? Then this pragma could help you from blowing away valuable data.

  Like the _noclobber_ variable of some shells, this module will prevent the
  use of open modes which truncate if a file already exists. This behavior
  can be controlled at the block level, as demonstrated in the SYNOPSIS.


name: perl-common-sense
arch: noarch
version: 3.75
epoch: 0
release: 1.1
summary: Save a tree AND a kitten, use common::sense!
url: https://metacpan.org/release/common-sense
rpm_license: CHECK(Artistic-1.0 OR GPL-1.0-or-later)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: goat13
rpm_sourcerpm: perl-common-sense-3.75-1.1.src.rpm
location_href: noarch/perl-common-sense-3.75-1.1.noarch.rpm
checksum_type: sha512
pkgId:
  1bddc81088c4ed59580bb5333be869af487ad14ddc459d854595b51de9d9a0f3e2ed95c86e981c7165897824271cc1fb704421452281ce68c1da39cca37de69b

description:
     “Nothing is more fairly distributed than common sense: no one thinks
     he needs more of it than he already has.”

     – René Descartes

  This module implements some sane defaults for Perl programs, as defined by
  two typical (or not so typical - use your common sense) specimens of Perl
  coders. In fact, after working out details on which warnings and strict
  modes to enable and make fatal, we found that we (and our code written so
  far, and others) fully agree on every option, even though we never used
  warnings before, so it seems this module indeed reflects a "common" sense
  among some long-time Perl coders.

  The basic philosophy behind the choices made in common::sense can be
  summarised as: "enforcing strict policies to catch as many bugs as
  possible, while at the same time, not limiting the expressive power
  available to the programmer".

  Two typical examples of how this philosophy is applied in practise is the
  handling of uninitialised and malloc warnings:

  * _uninitialised_

  'undef' is a well-defined feature of perl, and enabling warnings for using
  it rarely catches any bugs, but considerably limits you in what you can do,
  so uninitialised warnings are disabled.

  * _malloc_

  Freeing something twice on the C level is a serious bug, usually causing
  memory corruption. It often leads to side effects much later in the program
  and there are no advantages to not reporting this, so malloc warnings are
  fatal by default.

  Unfortunately, there is no fine-grained warning control in perl, so often
  whole groups of useful warnings had to be excluded because of a single
  useless warning (for example, perl puts an arbitrary limit on the length of
  text you can match with some regexes before emitting a warning, making the
  whole 'regexp' category useless).

  What follows is a more thorough discussion of what this module does, and
  why it does it, and what the advantages (and disadvantages) of this
  approach are.


name: perl-common-sense
arch: src
version: 3.75
epoch: 0
release: 1.1
summary: Save a tree AND a kitten, use common::sense!
url: https://metacpan.org/release/common-sense
rpm_license: CHECK(Artistic-1.0 OR GPL-1.0-or-later)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: goat13
location_href: src/perl-common-sense-3.75-1.1.src.rpm
checksum_type: sha512
pkgId:
  eeb572ebf62a4682bf15fc78ef6302a2f1a1b15dd6958ba46c37808c361ca9abc7a2a65215d8d51e62bd0e9950645a4284d36bef75cd6f25f87c01aa4b682aac

description:
     “Nothing is more fairly distributed than common sense: no one thinks
     he needs more of it than he already has.”

     – René Descartes

  This module implements some sane defaults for Perl programs, as defined by
  two typical (or not so typical - use your common sense) specimens of Perl
  coders. In fact, after working out details on which warnings and strict
  modes to enable and make fatal, we found that we (and our code written so
  far, and others) fully agree on every option, even though we never used
  warnings before, so it seems this module indeed reflects a "common" sense
  among some long-time Perl coders.

  The basic philosophy behind the choices made in common::sense can be
  summarised as: "enforcing strict policies to catch as many bugs as
  possible, while at the same time, not limiting the expressive power
  available to the programmer".

  Two typical examples of how this philosophy is applied in practise is the
  handling of uninitialised and malloc warnings:

  * _uninitialised_

  'undef' is a well-defined feature of perl, and enabling warnings for using
  it rarely catches any bugs, but considerably limits you in what you can do,
  so uninitialised warnings are disabled.

  * _malloc_

  Freeing something twice on the C level is a serious bug, usually causing
  memory corruption. It often leads to side effects much later in the program
  and there are no advantages to not reporting this, so malloc warnings are
  fatal by default.

  Unfortunately, there is no fine-grained warning control in perl, so often
  whole groups of useful warnings had to be excluded because of a single
  useless warning (for example, perl puts an arbitrary limit on the length of
  text you can match with some regexes before emitting a warning, making the
  whole 'regexp' category useless).

  What follows is a more thorough discussion of what this module does, and
  why it does it, and what the advantages (and disadvantages) of this
  approach are.


name: perl-conjury
arch: noarch
version: 1.004
epoch: 0
release: 7.448
summary: Conjury Perl Module
description: conjury Perl module
url: http://search.cpan.org/dist/conjury/
rpm_license: CHECK(GPL-1.0+ or Artistic-1.0)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: sheep83
rpm_sourcerpm: perl-conjury-1.004-7.448.src.rpm
location_href: noarch/perl-conjury-1.004-7.448.noarch.rpm
checksum_type: sha512
pkgId:
  43076c528352b60b95e52c5c22664c339046e66ad35d317eff5d34a79cc064acbad0a00cb34d5a1cd93ec597443713389e1882c106105c4a2550541b0365b108


name: perl-conjury
arch: src
version: 1.004
epoch: 0
release: 7.448
summary: Conjury Perl Module
description: conjury Perl module
url: http://search.cpan.org/dist/conjury/
rpm_license: CHECK(GPL-1.0+ or Artistic-1.0)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: sheep83
location_href: src/perl-conjury-1.004-7.448.src.rpm
checksum_type: sha512
pkgId:
  5d4b6fb3cb33b3a328d76bfa6faba8663fe2a3a3b062ecb2180f2c587a45623551b903078769ccb77ef3a14ca1e7ad5626786e17c4a494487942e478a2c27559


name: perl-constant
arch: noarch
version: 1.33
epoch: 0
release: 2.57
summary: Perl pragma to declare constants
url: http://search.cpan.org/dist/constant/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus3
rpm_sourcerpm: perl-constant-1.33-2.57.src.rpm
location_href: noarch/perl-constant-1.33-2.57.noarch.rpm
checksum_type: sha512
pkgId:
  05f50b0c0135362be4087bbdb19aa105f9f998a4db1a61d159bdbbe387acc6d2b7bbadcf1461c18721a69b30d9e329ac3fdb03741a21f48f75c8ae6d17745631

description:
  This pragma allows you to declare constants at compile-time.

  When you declare a constant such as 'PI' using the method shown above, each
  machine your script runs upon can have as many digits of accuracy as it can
  use. Also, your program will be easier to read, more likely to be
  maintained (and maintained correctly), and far less likely to send a space
  probe to the wrong planet because nobody noticed the one equation in which
  you wrote '3.14195'.

  When a constant is used in an expression, Perl replaces it with its value
  at compile time, and may then optimize the expression further. In
  particular, any code in an 'if (CONSTANT)' block will be optimized away if
  the constant is false.


name: perl-constant
arch: src
version: 1.33
epoch: 0
release: 2.57
summary: Perl pragma to declare constants
url: http://search.cpan.org/dist/constant/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus3
location_href: src/perl-constant-1.33-2.57.src.rpm
checksum_type: sha512
pkgId:
  86c4f98e987bf33f7e8dd788d3777ab09bf9519e353a25b6a551a33f978ae79d12e3276a72886dce911d7a60ffee7a9776229646999f13e242046e58d70287e5

description:
  This pragma allows you to declare constants at compile-time.

  When you declare a constant such as 'PI' using the method shown above, each
  machine your script runs upon can have as many digits of accuracy as it can
  use. Also, your program will be easier to read, more likely to be
  maintained (and maintained correctly), and far less likely to send a space
  probe to the wrong planet because nobody noticed the one equation in which
  you wrote '3.14195'.

  When a constant is used in an expression, Perl replaces it with its value
  at compile time, and may then optimize the expression further. In
  particular, any code in an 'if (CONSTANT)' block will be optimized away if
  the constant is false.


name: perl-constant-Atom
arch: noarch
version: 0.11
epoch: 0
release: 1.25
summary: Define unique symbols (constant functions with opaque values)
url: https://metacpan.org/release/constant-Atom
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Unspecified
rpm_buildhost: hurricane3
rpm_sourcerpm: perl-constant-Atom-0.11-1.25.src.rpm
location_href: noarch/perl-constant-Atom-0.11-1.25.noarch.rpm
checksum_type: sha512
pkgId:
  ebf1993c35949bb9ab70f325f38dffdf117742c89f68d016e059d3a3ce6459b3cfb1a0691b6dd00af3636f439bb39ae9d75fe8c1db0be3e9ad2e3ed0cc998dee

description:
  This module is used to declare 'function constants', similar to those
  created with constant and enum, but with a key difference: you don't
  specify a value for the constants, and you should use it in situations
  where you don't need to know the value.

  Atoms have their own independent identity, and will only compare positively
  (via the 'eq' test) with other identical Atoms. All other operations on
  Atoms are undefined, including casting to a string and casting to a number.

  Atoms are used in place of constants in situations where a unique value is
  needed to represent some idea or program state, but where that value is not
  naturally associated with a scalar value, and shouldn't be confused with
  one. Atoms are similar to C enums in this respect, except that Atoms do not
  have an ordinal value.

  For example, you might use constant or enum where you want to define
  constants that are used to index an array. 'constant::Atom' can't be used
  in such situations.

  Below is an example of where an Atom would solve a problem:

   
     use constant 'error' => 999999;

     sub bar {
         my($arg) = @_;

         
         return 1 ? $arg : error;
     }

     my $foo = bar(999999);
     print "Foo: $foo\n";

     print $foo eq error ? "Foo returned error." : "Foo returned $foo.";

  Output: Foo returned error.

  In the above example, the programmer is trying to choose some unlikely
  value to alias 'error' to. The problem is, if 'bar' is ever accidently
  called with this same value, the program will mistakenly believe that
  'error' had been returned.

  This doesn't happen with Atoms.

      use constant::Atom 'error';
   

      sub bar {
          my($arg) = @_;

          
          return 1 ? $arg : error;
      }

      my $foo = bar(999999);
      print "Foo: $foo\n";

      print $foo eq error ? "Foo returned error." : "Foo returned $foo.";

  Output: Foo returned 999999.


name: perl-constant-Atom
arch: src
version: 0.11
epoch: 0
release: 1.25
summary: Define unique symbols (constant functions with opaque values)
url: https://metacpan.org/release/constant-Atom
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Unspecified
rpm_buildhost: hurricane3
location_href: src/perl-constant-Atom-0.11-1.25.src.rpm
checksum_type: sha512
pkgId:
  1dc86841159fbaf983f7d37a0a8b3fcdeba11e1e31096822e747958817f88513674deb2d97460b447faa429caaf7a878eb891932ff651af180fb6831832b1893

description:
  This module is used to declare 'function constants', similar to those
  created with constant and enum, but with a key difference: you don't
  specify a value for the constants, and you should use it in situations
  where you don't need to know the value.

  Atoms have their own independent identity, and will only compare positively
  (via the 'eq' test) with other identical Atoms. All other operations on
  Atoms are undefined, including casting to a string and casting to a number.

  Atoms are used in place of constants in situations where a unique value is
  needed to represent some idea or program state, but where that value is not
  naturally associated with a scalar value, and shouldn't be confused with
  one. Atoms are similar to C enums in this respect, except that Atoms do not
  have an ordinal value.

  For example, you might use constant or enum where you want to define
  constants that are used to index an array. 'constant::Atom' can't be used
  in such situations.

  Below is an example of where an Atom would solve a problem:

   
     use constant 'error' => 999999;

     sub bar {
         my($arg) = @_;

         
         return 1 ? $arg : error;
     }

     my $foo = bar(999999);
     print "Foo: $foo\n";

     print $foo eq error ? "Foo returned error." : "Foo returned $foo.";

  Output: Foo returned error.

  In the above example, the programmer is trying to choose some unlikely
  value to alias 'error' to. The problem is, if 'bar' is ever accidently
  called with this same value, the program will mistakenly believe that
  'error' had been returned.

  This doesn't happen with Atoms.

      use constant::Atom 'error';
   

      sub bar {
          my($arg) = @_;

          
          return 1 ? $arg : error;
      }

      my $foo = bar(999999);
      print "Foo: $foo\n";

      print $foo eq error ? "Foo returned error." : "Foo returned $foo.";

  Output: Foo returned 999999.


name: perl-constant-boolean
arch: noarch
version: 0.02
epoch: 0
release: 1.49
summary: Define TRUE and FALSE constants
url: http://search.cpan.org/dist/constant-boolean/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: hci-snode2-m0
rpm_sourcerpm: perl-constant-boolean-0.02-1.49.src.rpm
location_href: noarch/perl-constant-boolean-0.02-1.49.noarch.rpm
checksum_type: sha512
pkgId:
  e27aad064295a52365b179039c310237bee9f262b7af94fa97f074627c43d9cfdd2f6b4cacf2ef340efb6fd1f581f18b6f5106a255a6632c33f85ce9effc656a

description:
  Defines 'TRUE' and 'FALSE' constants in caller's namespace. You could use
  simple values like empty string or zero for false, or any non-empty and
  non-zero string value as true, but the 'TRUE' and 'FALSE' constants are
  more descriptive.

  It is virtually the same as:

    
    use constant TRUE => !! 1;
    use constant FALSE => !! '';

  The constants exported by 'constant::boolean' are not reported by
  Test::Pod::Coverage, so it is more convenient to use this module than to
  define 'TRUE' and 'FALSE' constants by yourself.

  The constants can be removed from class API with 'no constant::boolean'
  pragma or some universal tool like namespace::clean.


name: perl-constant-boolean
arch: src
version: 0.02
epoch: 0
release: 1.49
summary: Define TRUE and FALSE constants
url: http://search.cpan.org/dist/constant-boolean/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: hci-snode2-m0
location_href: src/perl-constant-boolean-0.02-1.49.src.rpm
checksum_type: sha512
pkgId:
  20f3fd758636ce3d1888d6e33aec50b8cdee329789922887cd738596d85e69ab596cdbb280532f254d485a040fcd157f7e2c3cce8963cf84debaeb4b6b796f9d

description:
  Defines 'TRUE' and 'FALSE' constants in caller's namespace. You could use
  simple values like empty string or zero for false, or any non-empty and
  non-zero string value as true, but the 'TRUE' and 'FALSE' constants are
  more descriptive.

  It is virtually the same as:

    
    use constant TRUE => !! 1;
    use constant FALSE => !! '';

  The constants exported by 'constant::boolean' are not reported by
  Test::Pod::Coverage, so it is more convenient to use this module than to
  define 'TRUE' and 'FALSE' constants by yourself.

  The constants can be removed from class API with 'no constant::boolean'
  pragma or some universal tool like namespace::clean.


name: perl-constant-defer
arch: noarch
version: 6
epoch: 0
release: 1.49
summary: Constant Subs with Deferred Value Calculation
url: http://search.cpan.org/dist/constant-defer/
rpm_license: GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: stones
rpm_sourcerpm: perl-constant-defer-6-1.49.src.rpm
location_href: noarch/perl-constant-defer-6-1.49.noarch.rpm
checksum_type: sha512
pkgId:
  a5a23477c3130e5b70d58bdf97bea8a9ac2f352d8d8e1eb596590e24c1c6136dc891f6bce7e79b5a400dc1e5a500b6a157add80877ad209574e2be6f2ddcf2a4

description:
  'constant::defer' creates a subroutine which on the first call runs given
  code to calculate its value, and on any subsequent calls just returns that
  value, like a constant. The value code is discarded once run, allowing it
  to be garbage collected.

  Deferring a calculation is good if it might take a lot of work or produce a
  big result but is only needed sometimes or only well into a program run. If
  it's never needed then the value code never runs.

  A deferred constant is generally not inlined or folded (see perlop/Constant
  Folding) since it's not a single scalar value. In the current
  implementation a deferred constant becomes a plain constant after the first
  use, so may inline etc in code compiled after that (see IMPLEMENTATION
  below).

  See _examples/simple.pl_ in the constant-defer source code for a complete
  sample program.


name: perl-constant-defer
arch: src
version: 6
epoch: 0
release: 1.49
summary: Constant Subs with Deferred Value Calculation
url: http://search.cpan.org/dist/constant-defer/
rpm_license: GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: stones
location_href: src/perl-constant-defer-6-1.49.src.rpm
checksum_type: sha512
pkgId:
  66d9ed27b48389cdc32797b3fc03e5b1166f04abe2ca3f5412a6958983a875e9a0be21bdd7812430e7753108992ae306a79bf47f05ea077161ce23d86dd2374b

description:
  'constant::defer' creates a subroutine which on the first call runs given
  code to calculate its value, and on any subsequent calls just returns that
  value, like a constant. The value code is discarded once run, allowing it
  to be garbage collected.

  Deferring a calculation is good if it might take a lot of work or produce a
  big result but is only needed sometimes or only well into a program run. If
  it's never needed then the value code never runs.

  A deferred constant is generally not inlined or folded (see perlop/Constant
  Folding) since it's not a single scalar value. In the current
  implementation a deferred constant becomes a plain constant after the first
  use, so may inline etc in code compiled after that (see IMPLEMENTATION
  below).

  See _examples/simple.pl_ in the constant-defer source code for a complete
  sample program.


name: perl-constant-lexical
arch: src
version: 2.0003
epoch: 0
release: 1.57
summary: Perl pragma to declare lexical compile-time constants
url: http://search.cpan.org/dist/constant-lexical/
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: sheep87
location_href: src/perl-constant-lexical-2.0003-1.57.src.rpm
checksum_type: sha512
pkgId:
  4f4bf4f41a8b56d89329e8b4af0e32d718fd942ab508eb2a0e67c0ba632c9e79a36cdf2650700683f66b8e08280d3ba64e5dc2d28f0ebeb62202794d7270936e

description:
  This module creates compile-time constants in the manner of constant.pm,
  but makes them local to the enclosing scope.

rpm_license:
  cpan dot org) This program is free software and you may redistribute or modify it(or both)under the same terms as perl.


name: perl-constant-lexical
arch: x86_64
version: 2.0003
epoch: 0
release: 1.57
summary: Perl pragma to declare lexical compile-time constants
url: http://search.cpan.org/dist/constant-lexical/
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: sheep87
rpm_sourcerpm: perl-constant-lexical-2.0003-1.57.src.rpm
location_href: x86_64/perl-constant-lexical-2.0003-1.57.x86_64.rpm
checksum_type: sha512
pkgId:
  ae0c1f7f030ac8d4a15ea3318ad0eab66c9bb04ee2f7f92b69b22192c4fc55bc86449374da922ed49aa2fb81cde6a1996cf94e59bae1b0d59559eeb4b249c60e

description:
  This module creates compile-time constants in the manner of constant.pm,
  but makes them local to the enclosing scope.

rpm_license:
  cpan dot org) This program is free software and you may redistribute or modify it(or both)under the same terms as perl.


name: perl-constant-more
arch: noarch
version: 0.1.2
epoch: 0
release: 1.4
summary: Assign values to constants from the command arguments
url: https://metacpan.org/release/constant-more
rpm_license: MIT
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Unspecified
rpm_buildhost: cloud135
rpm_sourcerpm: perl-constant-more-0.1.2-1.4.src.rpm
location_href: noarch/perl-constant-more-0.1.2-1.4.noarch.rpm
checksum_type: sha512
pkgId:
  5bf8e3d86c2fd14ee78450dad6f39a075096d0d8e81515d82618887f09581297e3f5efa8f8536331bb9a6ed5bbeeb7af51d29176c5e8ea88fa3eccb9961ab3c6

description:
  Performs the similar tasks as 'use constant', but adds features to assign
  values of constants from the command line or environment variables.

  In addition, constants are only defined/set if they don't exist already,
  making configuring and overriding constants defined in sub modules
  possible. A module can specify a default value which is used if the
  constant hasn't been defined by the top level script.

  GetOpt::Long option specification is used for processing command line
  options to give flexibility in how and what switches are used. To save on
  memory, GetOpt::Long is only loaded if option processing is wanted (i.e.
  the 'opt' field is specified).

  In advanced form, a user subroutine can be supplied to give control of
  processing. This is used by Log::OK for example to generate multiple
  constants from a single input level.


name: perl-constant-more
arch: src
version: 0.1.2
epoch: 0
release: 1.4
summary: Assign values to constants from the command arguments
url: https://metacpan.org/release/constant-more
rpm_license: MIT
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Unspecified
rpm_buildhost: cloud135
location_href: src/perl-constant-more-0.1.2-1.4.src.rpm
checksum_type: sha512
pkgId:
  e567917b5b872cdb224d685826b13d5a1695b84e16b1c0f0bc16f0acfbe1b166e7d03eba959dae16dbcc7c4c8b97a01f07c700d53439bef352e0ef1cbc0cc42f

description:
  Performs the similar tasks as 'use constant', but adds features to assign
  values of constants from the command line or environment variables.

  In addition, constants are only defined/set if they don't exist already,
  making configuring and overriding constants defined in sub modules
  possible. A module can specify a default value which is used if the
  constant hasn't been defined by the top level script.

  GetOpt::Long option specification is used for processing command line
  options to give flexibility in how and what switches are used. To save on
  memory, GetOpt::Long is only loaded if option processing is wanted (i.e.
  the 'opt' field is specified).

  In advanced form, a user subroutine can be supplied to give control of
  processing. This is used by Log::OK for example to generate multiple
  constants from a single input level.


name: perl-constant-our
arch: noarch
version: 0.07
epoch: 0
release: 953.34
summary: Perl pragma to declare constants like our vars
url: https://metacpan.org/release/constant-our
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: wildcard2
rpm_sourcerpm: perl-constant-our-0.07-953.34.src.rpm
location_href: noarch/perl-constant-our-0.07-953.34.noarch.rpm
checksum_type: sha512
pkgId:
  9ec646663200227cb7b02e7468a39b92251cd565e9fac740ac39aabae618080d3712df05d33bb4e48e4f83c7b0fad328db6c2215809d263ef4e8d4d3c4dd3445

description:
  This pragma extends standard pragma 'constant'.

  As you may know, when a constant is used in an expression, Perl replaces it
  with its value at compile time, and may then optimize the expression
  further.

  You can inspect this behavior by yourself:

      $ perl -MO=Deparse -e'use constant{DEBUG => 1}; warn "1"; if(DEBUG){warn "2"} warn "3";'
      use constant ({'DEBUG', 1});
      warn '1';
      do {
          warn '2'
      };
      warn '3';

  All warns are here.

      $ perl -MO=Deparse -e'use constant{DEBUG => 0}; warn "1"; if(DEBUG){warn "2"} warn "3";'
      use constant ({'DEBUG', 0});
      warn '1';
      '???';
      warn '3';

  Notice the '???' instead of the second 'warn'.

  So you can do something like this:

      
      use constant DEBUG => 0;

      
      if(main::DEBUG)
      {
          
      }

  But you should declare all constants you use, you can't simply write

      if (main::DEBUG_SQL)
      {
      }

  without corresponding

      use constant DEBUG_SQL => 0;

  in the main script.

  With constant::our you can freely use "undeclared" constants in your
  condition statements.

      
      use constant::our {
          DEBUG => 1,
          DEBUG_CACHE => 1,
          };

      
      package My::Cool::Tools;
      use constant::our qw(DEBUG DEBUG_SQL); # don't need DEBUG_CACHE, but want (undeclared) DEBUG_SQL

      DEBUG && warn "DEBUG: $debug_info";              # DEBUG --> 1
      DEBUG && DEBUG_SQL && warn "DEBUG_SQL: $query";  # DEBUG_SQL --> undef

      stderr:
      "DEBUG: ..."


name: perl-constant-our
arch: src
version: 0.07
epoch: 0
release: 953.34
summary: Perl pragma to declare constants like our vars
url: https://metacpan.org/release/constant-our
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: wildcard2
location_href: src/perl-constant-our-0.07-953.34.src.rpm
checksum_type: sha512
pkgId:
  a723d6c309c6dc14c1ef279bc74e27983df3a2f868d95450b885093e5e73fa4859b85b8a9318785b8362443111ca5e826a092cd199b34b7f207007665a584180

description:
  This pragma extends standard pragma 'constant'.

  As you may know, when a constant is used in an expression, Perl replaces it
  with its value at compile time, and may then optimize the expression
  further.

  You can inspect this behavior by yourself:

      $ perl -MO=Deparse -e'use constant{DEBUG => 1}; warn "1"; if(DEBUG){warn "2"} warn "3";'
      use constant ({'DEBUG', 1});
      warn '1';
      do {
          warn '2'
      };
      warn '3';

  All warns are here.

      $ perl -MO=Deparse -e'use constant{DEBUG => 0}; warn "1"; if(DEBUG){warn "2"} warn "3";'
      use constant ({'DEBUG', 0});
      warn '1';
      '???';
      warn '3';

  Notice the '???' instead of the second 'warn'.

  So you can do something like this:

      
      use constant DEBUG => 0;

      
      if(main::DEBUG)
      {
          
      }

  But you should declare all constants you use, you can't simply write

      if (main::DEBUG_SQL)
      {
      }

  without corresponding

      use constant DEBUG_SQL => 0;

  in the main script.

  With constant::our you can freely use "undeclared" constants in your
  condition statements.

      
      use constant::our {
          DEBUG => 1,
          DEBUG_CACHE => 1,
          };

      
      package My::Cool::Tools;
      use constant::our qw(DEBUG DEBUG_SQL); # don't need DEBUG_CACHE, but want (undeclared) DEBUG_SQL

      DEBUG && warn "DEBUG: $debug_info";              # DEBUG --> 1
      DEBUG && DEBUG_SQL && warn "DEBUG_SQL: $query";  # DEBUG_SQL --> undef

      stderr:
      "DEBUG: ..."


name: perl-constant-override
arch: noarch
version: 0.01
epoch: 0
release: 3.51
summary: Override/ignore constants
url: http://search.cpan.org/dist/constant-override/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus1
rpm_sourcerpm: perl-constant-override-0.01-3.51.src.rpm
location_href: noarch/perl-constant-override-0.01-3.51.noarch.rpm
checksum_type: sha512
pkgId:
  80fc8ff8114d97b83ac0b33d97de2c3519285fa6962fcca1505cecc4ab2b8e822c59f897303feb1f9c9cd2ad42462ba1489ae125e5e240b49d705a829d3f492e

description:
  Provides for overriding 'constant''s import method, so that the 'constant'
  functions can be replaced with your own functions/values, or ignored
  altogether.

  'use constant::override ...' statements must occur before 'use constant
  ...' statements.


name: perl-constant-override
arch: src
version: 0.01
epoch: 0
release: 3.51
summary: Override/ignore constants
url: http://search.cpan.org/dist/constant-override/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus1
location_href: src/perl-constant-override-0.01-3.51.src.rpm
checksum_type: sha512
pkgId:
  f34c054dea203c6cfeee637b750c74bb9f2c79b6ebdeb66546f0b9c7155d82d2f990a6b84680c572a70f5e41566007a73a017b68b78986ac1102b7fe5388031a

description:
  Provides for overriding 'constant''s import method, so that the 'constant'
  functions can be replaced with your own functions/values, or ignored
  altogether.

  'use constant::override ...' statements must occur before 'use constant
  ...' statements.


name: perl-constant-tiny
arch: noarch
version: 1.02
epoch: 0
release: 2.26
summary: Perl pragma to declare constants
url: http://search.cpan.org/dist/constant-tiny/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb01
rpm_sourcerpm: perl-constant-tiny-1.02-2.26.src.rpm
location_href: noarch/perl-constant-tiny-1.02-2.26.noarch.rpm
checksum_type: sha512
pkgId:
  019262bed863306f41106fcca13007fab0a031a2107096f713e94f0f72e387f8963d704d47e64dcd1a5b8a5593aec1abcb02e0472df0b897e665204f3cfc4b47

description:
  This module is a lightweight version of the Perl standard module
  'constant.pm'. Here are the keys differences:

    * only works on Perl 5.10+ in order to simplify a good part of the code

    * doesn't support Unicode names; please use the standard 'constant.pm' module
  if you need to create constants with Unicode names

    * stricter rules about valid names, only allow names with alphanums
  ('[a-zA-Z0-9]' and underscore ('_'), allowing one optional leading
  underscore

  In order to simplify its usage, 'constant:tiny' uses the normal 'constant'
  API. The main advatange is that switching your code to 'constant::tiny'
  means simply adding it before the first 'use constant'. The disadvantage is
  that, obviously, both modules can't be used at the same time. If the normal
  'constant' was loaded before 'constant::tiny', the latter won't do
  anything, letting the normal 'constant' do the work.

  Other than this, the usage is (nearly) exactly the same as with the
  standard 'constant' module. For more details, please read constant.


name: perl-constant-tiny
arch: src
version: 1.02
epoch: 0
release: 2.26
summary: Perl pragma to declare constants
url: http://search.cpan.org/dist/constant-tiny/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb01
location_href: src/perl-constant-tiny-1.02-2.26.src.rpm
checksum_type: sha512
pkgId:
  05309726008bdce25cfd6c0eb27bb995fe31b1bbf25a73bd17d9ea88eb9dc749c67e5c4f250b47057cde7f728a3a923ee2704a3a9e240ae5e94cfc004757384a

description:
  This module is a lightweight version of the Perl standard module
  'constant.pm'. Here are the keys differences:

    * only works on Perl 5.10+ in order to simplify a good part of the code

    * doesn't support Unicode names; please use the standard 'constant.pm' module
  if you need to create constants with Unicode names

    * stricter rules about valid names, only allow names with alphanums
  ('[a-zA-Z0-9]' and underscore ('_'), allowing one optional leading
  underscore

  In order to simplify its usage, 'constant:tiny' uses the normal 'constant'
  API. The main advatange is that switching your code to 'constant::tiny'
  means simply adding it before the first 'use constant'. The disadvantage is
  that, obviously, both modules can't be used at the same time. If the normal
  'constant' was loaded before 'constant::tiny', the latter won't do
  anything, letting the normal 'constant' do the work.

  Other than this, the usage is (nearly) exactly the same as with the
  standard 'constant' module. For more details, please read constant.


name: perl-continuous-delivery-template
arch: noarch
version: 0.02
epoch: 0
release: 1.43
summary: Continuous Delivery Workflow Dockerhub, Gitlab, and Cpan
url: http://search.cpan.org/dist/continuous-delivery-template/
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: hci-cnode1-e5
rpm_sourcerpm: perl-continuous-delivery-template-0.02-1.43.src.rpm
location_href: noarch/perl-continuous-delivery-template-0.02-1.43.noarch.rpm
checksum_type: sha512
pkgId:
  cfeac33816741b287692f6a53c5eeff69b7fef4302e95b29c50cc4769e9755f27fe10fee54df38971ef0e2d3113e3e1943e7ae22f809856772009adea0eb0506

description:
  Perl template application configured to use Gitlab CI/CD service as
  continuous delivery workflow.

  On the Perl side, this application template uses Dist::Zilla as building,
  testing and releasing framework.

     hack on application code
     git commit ...
     git push

  This will trigger building, testing and publishing the docker image with
  :ci tag to dockerhub.

  If all tests pass and you are going to release a new version should use
  Dist::Zila as follows:

     dzil release

  Dist::Zilla will create a new git tag based on version number on
  lib/continuous/delivery/template.pm file and push the tag to github.

  Dist::Zilla will publish the release on CPAN, the CPAN will run tests under
  a variety of platforns and environments throught CPANTESTERS.

  When a new git tag is created on gitlab repository, the pipeline will build
  the stages: build -> test -> deploy. The deploy stage is executed only when
  a new tag is pushed to repository.

  The deploy job will upload a stable image to dockerhub Container Registry.

  Before you can upload Perl modules to CPAN you need to create an account on
  The [Perl programming] Authors Upload Server:

    * https://pause.perl.org

  You need create an account on Docker Hub Container Regitry and configure
  the following secret variables on Gitlab CI / CD settings:

  * $DOCKER_USER

  Your username on hub.docker.com.

  * $DOCKER_PASSWORD

  Your password on hub.docker.com.


name: perl-continuous-delivery-template
arch: src
version: 0.02
epoch: 0
release: 1.43
summary: Continuous Delivery Workflow Dockerhub, Gitlab, and Cpan
url: http://search.cpan.org/dist/continuous-delivery-template/
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: hci-cnode1-e5
location_href: src/perl-continuous-delivery-template-0.02-1.43.src.rpm
checksum_type: sha512
pkgId:
  daeaf95ef337d643886eef076bff466104b3109b646299bca9a0855ebacc3e44cfe9c8454d47d02c56947ff2c74b77e478ccaeab36bbaf215fe036588824e39b

description:
  Perl template application configured to use Gitlab CI/CD service as
  continuous delivery workflow.

  On the Perl side, this application template uses Dist::Zilla as building,
  testing and releasing framework.

     hack on application code
     git commit ...
     git push

  This will trigger building, testing and publishing the docker image with
  :ci tag to dockerhub.

  If all tests pass and you are going to release a new version should use
  Dist::Zila as follows:

     dzil release

  Dist::Zilla will create a new git tag based on version number on
  lib/continuous/delivery/template.pm file and push the tag to github.

  Dist::Zilla will publish the release on CPAN, the CPAN will run tests under
  a variety of platforns and environments throught CPANTESTERS.

  When a new git tag is created on gitlab repository, the pipeline will build
  the stages: build -> test -> deploy. The deploy stage is executed only when
  a new tag is pushed to repository.

  The deploy job will upload a stable image to dockerhub Container Registry.

  Before you can upload Perl modules to CPAN you need to create an account on
  The [Perl programming] Authors Upload Server:

    * https://pause.perl.org

  You need create an account on Docker Hub Container Regitry and configure
  the following secret variables on Gitlab CI / CD settings:

  * $DOCKER_USER

  Your username on hub.docker.com.

  * $DOCKER_PASSWORD

  Your password on hub.docker.com.


name: perl-coroutine0
arch: noarch
version: 0.02
epoch: 0
release: 8.55
summary: Working but Ugly Coroutine Generator
url: http://search.cpan.org/dist/coroutine0/
rpm_license: GPL-1.0+ or Artistic-1.0
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: cloud107
rpm_sourcerpm: perl-coroutine0-0.02-8.55.src.rpm
location_href: noarch/perl-coroutine0-0.02-8.55.noarch.rpm
checksum_type: sha512
pkgId:
  f4762eaebe02b0c4fc2e96020af731ae2528d267a54e9d3aea02fb91249b98b6ade979f8c1c46add99158e1892abf291415857d80d33c1ba2a28f7ff73742e4a

description:
  'new' takes a list and returns a blessed coderef. The defined argument keys
  include 'VARS' and 'BODY'. Lexicals meant to persist between calls to a
  routine are listed in 'VARS'.

  The 'new' function works by rewriting each instance of /\bYIELD\b.*;/
  within the body to a labeled exit/entry point and wrapping the rewritten
  body in an anonymous subroutine generator.

  Define 'TIDY' to a true value to suppress caching the extended coroutine
  source code. This breaks 'copy'.

  You can make another coroutine with its own pad by calling the 'copy'
  method, which evals the wrapped body again.

  define a 'PRE' argument to include some code to run every time the coro is
  called, before going to the entry point.

  define a 'DIE' argument to have 'new' tell you all about it as soon as the
  body is rewritten.

  When the execution falls out of the bottom of the body, an 'undef' is
  returned and the execution point is reset to the begining of the body.
  Variables are not cleared and will keep values from previous times through
  the routine.


name: perl-coroutine0
arch: src
version: 0.02
epoch: 0
release: 8.55
summary: Working but Ugly Coroutine Generator
url: http://search.cpan.org/dist/coroutine0/
rpm_license: GPL-1.0+ or Artistic-1.0
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: cloud107
location_href: src/perl-coroutine0-0.02-8.55.src.rpm
checksum_type: sha512
pkgId:
  620dcbf232e58aa2d64932b03346bbaf36286a64f9f586195c56795385d29db4c8b0dc3bab99da340f4e2affaf2226dab9101264fe60487c7a5f8f4e4006d623

description:
  'new' takes a list and returns a blessed coderef. The defined argument keys
  include 'VARS' and 'BODY'. Lexicals meant to persist between calls to a
  routine are listed in 'VARS'.

  The 'new' function works by rewriting each instance of /\bYIELD\b.*;/
  within the body to a labeled exit/entry point and wrapping the rewritten
  body in an anonymous subroutine generator.

  Define 'TIDY' to a true value to suppress caching the extended coroutine
  source code. This breaks 'copy'.

  You can make another coroutine with its own pad by calling the 'copy'
  method, which evals the wrapped body again.

  define a 'PRE' argument to include some code to run every time the coro is
  called, before going to the entry point.

  define a 'DIE' argument to have 'new' tell you all about it as soon as the
  body is rewritten.

  When the execution falls out of the bottom of the body, an 'undef' is
  returned and the execution point is reset to the begining of the body.
  Variables are not cleared and will keep values from previous times through
  the routine.


name: perl-cpan-listchanges
arch: noarch
version: 0.08
epoch: 0
release: 1.38
summary: List Changes for Cpan Modules
description: list changes for CPAN modules
url: http://search.cpan.org/dist/cpan-listchanges/
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus4
rpm_sourcerpm: perl-cpan-listchanges-0.08-1.38.src.rpm
location_href: noarch/perl-cpan-listchanges-0.08-1.38.noarch.rpm
checksum_type: sha512
pkgId:
  60b5b56b429b6a556bdea4069cbd298559415f403e5deef49fb3751f5d6400e637e052b3a653cf787e110b80e9f2b4e23caa557d515a9f5a69bc4bcae003dafa


name: perl-cpan-listchanges
arch: src
version: 0.08
epoch: 0
release: 1.38
summary: List Changes for Cpan Modules
description: list changes for CPAN modules
url: http://search.cpan.org/dist/cpan-listchanges/
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus4
location_href: src/perl-cpan-listchanges-0.08-1.38.src.rpm
checksum_type: sha512
pkgId:
  06eeac6826a56235abc4c3c6530ab391920a29069d2ff4054b69cdf8382b6043350973262a9634d5335afd6b7f265bc1e3b795f322168e90f3abeb05216c01d0


name: perl-cpan-outdated
arch: noarch
version: 0.32
epoch: 0
release: 1.48
summary: Detect Outdated Cpan Modules in Your Environment
description: detect outdated CPAN modules in your environment.
url: http://search.cpan.org/dist/cpan-outdated/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus4
rpm_sourcerpm: perl-cpan-outdated-0.32-1.48.src.rpm
location_href: noarch/perl-cpan-outdated-0.32-1.48.noarch.rpm
checksum_type: sha512
pkgId:
  5b2c82e8d1536c567734360b8bf0cb6aa263163fd3d87b8963c4a19377c3b78f616008fa9f6c8fddd3ac276b344a1e040e58882fc7c76f33c5b59dbe7005c5fe


name: perl-cpan-outdated
arch: src
version: 0.32
epoch: 0
release: 1.48
summary: Detect Outdated Cpan Modules in Your Environment
description: detect outdated CPAN modules in your environment.
url: http://search.cpan.org/dist/cpan-outdated/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-cirrus4
location_href: src/perl-cpan-outdated-0.32-1.48.src.rpm
checksum_type: sha512
pkgId:
  854d0218afd9ea43dcef70d3464bc3f592ae98ec6bdc240996c703d09c6649dfee894920c66bd15b70519a3c8edccb196763ea3d8a76f532e5b6b9c8c2017b12


name: perl-crap
arch: noarch
version: 0.08
epoch: 0
release: 1.48
summary: Just Don't Take Any
url: http://search.cpan.org/dist/crap/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb14
rpm_sourcerpm: perl-crap-0.08-1.48.src.rpm
location_href: noarch/perl-crap-0.08-1.48.noarch.rpm
checksum_type: sha512
pkgId:
  c30bedc84c566a258808ad6222fa3e5f5dcd2ee632e8812876b2f8784d1e2a9ceb46654bdb0d580c14019c4e536a6329c0feecb1c5dcac692b7a5f05de4fe1cc

description:
  Enables strict and warnings without all the typing.

  It also makes 'STDOUT' 'hot' turning off buffering.

  To enable just type 'no crap' in your script.

  'use crap' disables strict and warnings and restores previous settings to
  'STDOUT' bufferingness.


name: perl-crap
arch: src
version: 0.08
epoch: 0
release: 1.48
summary: Just Don't Take Any
url: http://search.cpan.org/dist/crap/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb14
location_href: src/perl-crap-0.08-1.48.src.rpm
checksum_type: sha512
pkgId:
  4a08c241aa4089b22d2a3d4ee923961c42a48a7d6867b3a34feb9da7e121e919216603f85b3dc8aa607223f9944a6de218c701b874402f611f7716de6c660ed2

description:
  Enables strict and warnings without all the typing.

  It also makes 'STDOUT' 'hot' turning off buffering.

  To enable just type 'no crap' in your script.

  'use crap' disables strict and warnings and restores previous settings to
  'STDOUT' bufferingness.


name: perl-csv2txt
arch: noarch
version: 2.0
epoch: 0
release: 7.404
summary: Csv2txt Perl Module
description: csv2txt Perl module
url: http://search.cpan.org/dist/csv2txt/
rpm_license: CHECK(GPL-1.0+ or Artistic-1.0)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-atreju3
rpm_sourcerpm: perl-csv2txt-2.0-7.404.src.rpm
location_href: noarch/perl-csv2txt-2.0-7.404.noarch.rpm
checksum_type: sha512
pkgId:
  2dc397cb989f8de6e74a04e1866e30e58af5d38f6e31c90f898a280de5f5b0d8e9987967f1b921d6012024b784e69ac9042fb09e194bf3018940d40792c6c60d


name: perl-csv2txt
arch: src
version: 2.0
epoch: 0
release: 7.404
summary: Csv2txt Perl Module
description: csv2txt Perl module
url: http://search.cpan.org/dist/csv2txt/
rpm_license: CHECK(GPL-1.0+ or Artistic-1.0)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: old-atreju3
location_href: src/perl-csv2txt-2.0-7.404.src.rpm
checksum_type: sha512
pkgId:
  00575435b33c5df5783f8e5d9ada3278731894654b77eefa220910fb0fce4d588268d3636804d3418e7a02aceb0c7b8ec84317c12b50d3cb2682ea9ad8729fad


name: perl-ctflags
arch: noarch
version: 0.04
epoch: 0
release: 8.55
summary: Perl extension for compile time flags configuration
url: http://search.cpan.org/dist/ctflags/
rpm_license: GPL-1.0+ or Artistic-1.0
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb60
rpm_sourcerpm: perl-ctflags-0.04-8.55.src.rpm
location_href: noarch/perl-ctflags-0.04-8.55.noarch.rpm
checksum_type: sha512
pkgId:
  95c66279f8c060e1484dd33a3eaf2064ab70362c6c9652b2b1ebb1d77fdf026d16c2e3cdf2ad19f501678b6afc3e780c441d29c0abb4f813e4d5d627f378dd9a

description:
  'ctflags' and 'ctflags::parse' packages allow to dynamically set constants
  values at compile time (every time the perl script is run) based on
  environment variables or command line options.

  Conceptually, ctflags are unsigned integer variables named with a single
  letter ('a'..'z', 'A'..'Z', case matters), and structured in namespaces.

  Several ctflags with the same name can coexist as long as they live in
  different namespaces (as perl variables with the same name but living in
  different packages are different variables).

  Namespace names have to be valid perl identifiers composed of letters, the
  underscore char ('_') and numbers. The colon (':') can also be used to
  simulate nested namespaces.

  Examples of valid qualified ctflags names are...

    myapp:a        # ctflag a in namespace myapp
    myapp:A        # ctflag A in namespace myapp
    myapp:debug:c  # ctflag c in namespace myapp:debug
    otherapp:C     # ctflag C in namespace otherapp
    App3:A         # ctflag A in namespace App3

  A property of ctflags is that they do not need to be predefined to be used
  and their default value is 0.


name: perl-ctflags
arch: src
version: 0.04
epoch: 0
release: 8.55
summary: Perl extension for compile time flags configuration
url: http://search.cpan.org/dist/ctflags/
rpm_license: GPL-1.0+ or Artistic-1.0
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb60
location_href: src/perl-ctflags-0.04-8.55.src.rpm
checksum_type: sha512
pkgId:
  17b79eb955f91096550777bc2761ad3fc0b4d1de355293dae62fc083255066ab670e482b97787ec67bde8c91b727303696b31c0c9bc498bef18d6a6b11831801

description:
  'ctflags' and 'ctflags::parse' packages allow to dynamically set constants
  values at compile time (every time the perl script is run) based on
  environment variables or command line options.

  Conceptually, ctflags are unsigned integer variables named with a single
  letter ('a'..'z', 'A'..'Z', case matters), and structured in namespaces.

  Several ctflags with the same name can coexist as long as they live in
  different namespaces (as perl variables with the same name but living in
  different packages are different variables).

  Namespace names have to be valid perl identifiers composed of letters, the
  underscore char ('_') and numbers. The colon (':') can also be used to
  simulate nested namespaces.

  Examples of valid qualified ctflags names are...

    myapp:a        # ctflag a in namespace myapp
    myapp:A        # ctflag A in namespace myapp
    myapp:debug:c  # ctflag c in namespace myapp:debug
    otherapp:C     # ctflag C in namespace otherapp
    App3:A         # ctflag A in namespace App3

  A property of ctflags is that they do not need to be predefined to be used
  and their default value is 0.


name: perl-curl_ev
arch: noarch
version: 0.07
epoch: 0
release: 1.35
summary: Using Net::Curl::Multi with EV
description: Using Net::Curl::Multi with EV
url: http://search.cpan.org/dist/curl_ev/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb53
rpm_sourcerpm: perl-curl_ev-0.07-1.35.src.rpm
location_href: noarch/perl-curl_ev-0.07-1.35.noarch.rpm
checksum_type: sha512
pkgId:
  93ac98c065cf58ffe306a197063978fa82a9eeac7821975937840de6a875c107cacef15ff071ed95aace2e51c7dc6d8fb0d45e8db95961213d0d3e2d94764b51


name: perl-curl_ev
arch: src
version: 0.07
epoch: 0
release: 1.35
summary: Using Net::Curl::Multi with EV
description: Using Net::Curl::Multi with EV
url: http://search.cpan.org/dist/curl_ev/
rpm_license: Artistic-1.0 or GPL-1.0+
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: lamb53
location_href: src/perl-curl_ev-0.07-1.35.src.rpm
checksum_type: sha512
pkgId:
  652b851f668ed558174e8b7495576a97e940853c908a72843b0a672405665e7d7a3e3464ccebe4df53120e523cdf22b1ac30794ed7ce191877c5174075d0908a


name: perl-curry
arch: noarch
version: 2.000001
epoch: 0
release: 1.14
summary: Create automatic curried method call closures for any class or object
description: Create automatic curried method call closures for any class or object
url: https://metacpan.org/release/curry
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Unspecified
rpm_buildhost: sheep87
rpm_sourcerpm: perl-curry-2.000001-1.14.src.rpm
location_href: noarch/perl-curry-2.000001-1.14.noarch.rpm
checksum_type: sha512
pkgId:
  a5221accd02de4fd7a900b748d7ef20532ceaf95942100df8a024cf9ad2bc81fc90252dc3b3c0e5c771764e47849b13dec1a0f9a2cad1fb6592ace7c9f6d0f2f


name: perl-curry
arch: src
version: 2.000001
epoch: 0
release: 1.14
summary: Create automatic curried method call closures for any class or object
description: Create automatic curried method call closures for any class or object
url: https://metacpan.org/release/curry
rpm_license: Artistic-1.0 OR GPL-1.0-or-later
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Unspecified
rpm_buildhost: sheep87
location_href: src/perl-curry-2.000001-1.14.src.rpm
checksum_type: sha512
pkgId:
  8b7691410fff6f23fb8b3c801178192058ff5402e52f2ba71e48dd1da353d39fb2531eae96cabafea2dc3f1031a7b2ed414a19c71dcf438cde8661c41f280376


name: perl-cyrillic
arch: noarch
version: 1.05
epoch: 0
release: 7.62
summary: Cyrillic Perl Module
description: cyrillic Perl module
url: http://search.cpan.org/dist/cyrillic/
rpm_license: CHECK(GPL-1.0+ or Artistic-1.0)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: sheep86
rpm_sourcerpm: perl-cyrillic-1.05-7.62.src.rpm
location_href: noarch/perl-cyrillic-1.05-7.62.noarch.rpm
checksum_type: sha512
pkgId:
  f0a5c5b1fb016f50d9080d7e42b18ad7c7bd0ca735e72acd0e4e3acb56537f49bb0e4ccbdb6a25c3565af0197684e13667bc9d9d42c70c6cfe6566329caedfb6


name: perl-cyrillic
arch: src
version: 1.05
epoch: 0
release: 7.62
summary: Cyrillic Perl Module
description: cyrillic Perl module
url: http://search.cpan.org/dist/cyrillic/
rpm_license: CHECK(GPL-1.0+ or Artistic-1.0)
rpm_vendor: obs://build.opensuse.org/devel:languages:perl
rpm_group: Development/Libraries/Perl
rpm_buildhost: sheep86
location_href: src/perl-cyrillic-1.05-7.62.src.rpm
checksum_type: sha512
pkgId:
  817601454c537dddb55f7b15c22ad631391c58ce2b70f9c684c9171ab8fe74db3785765775eabbfb9a1eb8ea901e45cadd1cea9e901ba1b02b0dca1366ca46c0


