Linux workstation

Upstream software project

myrlyn

Package manager GUI

About myrlyn

Package manager GUI

This project links 2 native package records across 2 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

myrlyn repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.myrlyn: recorded package coverageopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
myrlyn
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-only
Metadata completeness
100/100 (not a software quality rating)
Source repository
Open source repository

Source-reported description

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

Myrlyn is a graphical package manager to select software packages and patterns for installation, update and removal. It uses libzypp as its backend and Qt as its GUI toolkit.

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 16.0

  1. myrlyn

    openSUSE Leap 16.0 / System/Packages / source myrlyn

    0.9.7-bp160.1.4

    Package manager GUI

    aarch64ppc64les390xx86_64leap-16.0

openSUSE Tumbleweed

  1. myrlyn

    openSUSE Tumbleweed / System/Packages / source myrlyn

    1.0.0-1.6

    Package manager GUI

    x86_64tumbleweed

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.