Upstream software project

jvyamlb

YAML processor for JRuby

About jvyamlb

YAML processor for JRuby

This project links 3 native package records across 3 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.jvyamlb: recorded package coverageopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
jvyamlb
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
MIT
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

YAML processor extracted from JRuby.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 15.6

  1. Package jvyamlb

    leap-15.6 (openSUSE Leap 15.6) (Development/Libraries/Java): YAML processor for JRuby

    0.2.5-bp156.3.8: noarch

    Source: jvyamlb

openSUSE Leap 16.0

  1. Package jvyamlb

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/Java): YAML processor for JRuby

    0.2.5-bp160.1.11: noarch

    Source: jvyamlb

openSUSE Tumbleweed

  1. Package jvyamlb

    tumbleweed (openSUSE Tumbleweed) (Development/Libraries/Java): YAML processor for JRuby

    0.2.5-20.18: noarch

    Source: jvyamlb

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.