Upstream software project

sugar-clock

Clock activity for Sugar

About sugar-clock

Clock activity for Sugar

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

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.sugar-clock: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
sugar-clock
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
GPL-3.0-or-later
Source repository
Not reported

Source-reported description

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

This activity displays time in analog, digital, and "natural" forms. The "natural" form will be an image of a sun or moon arcing across the sky, rising and setting as the day progresses. This is more than a simple clock; the user will be able to grab any element and readjust it, which will update each of the other elements. In this manner, hopefully the children can explore and understand different methods of telling time.

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.

Fedora 43

  1. Package sugar-clock

    43 (Fedora 43) (Unspecified): Clock activity for Sugar

    22.1-13.fc42: noarch

    Source: sugar-clock

Fedora 44

  1. Package sugar-clock

    44 (Fedora 44) (Unspecified): Clock activity for Sugar

    22.1-15.fc44: noarch

    Source: sugar-clock

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.