Upstream software project

gkrellm-cpupower

Gkrellm plugin - CPU Frequency

About gkrellm-cpupower

Gkrellm plugin - CPU Frequency

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

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

Project identity

Project
gkrellm-cpupower
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6, opensuse-tumbleweed
License expression
GPL-2.0+
Source repository
Open source repository

Source-reported description

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

A gkrellm2 plugin for displaying and manipulating CPU frequency

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 gkrellm-cpupower

    leap-15.6 (openSUSE Leap 15.6) (System/GUI/Other): Gkrellm plugin - CPU Frequency

    0.2-bp156.3.6: aarch64 ppc64le x86_64

    Source: gkrellm-cpupower

openSUSE Tumbleweed

  1. Package gkrellm-cpupower

    tumbleweed (openSUSE Tumbleweed) (System/GUI/Other): Gkrellm plugin - CPU Frequency

    0.2-2.35: x86_64

    Source: gkrellm-cpupower

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.