Upstream software project

perl-Mason-Tidy

Tidy HTML::Mason/Mason components

About perl-Mason-Tidy

Tidy HTML::Mason/Mason components

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.perl-Mason-Tidy: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
perl-Mason-Tidy
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
GPL-1.0-or-later OR Artistic-1.0-Perl
Source repository
Not reported

Source-reported description

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

Mason::Tidy is the engine used by masontidy. You can call this API from your own program instead of executing masontidy. masontidy tidies Mason 1 and Mason 2 components, using perltidy to format the Perl code that can be embedded in various places in the component. masontidy does not (yet) attempt to tidy the HTML or other non-Perl content in a component.

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 perl-Mason-Tidy

    43 (Fedora 43) (Unspecified): Tidy HTML::Mason/Mason components

    2.57-30.fc43: noarch

    Source: perl-Mason-Tidy

Fedora 44

  1. Package perl-Mason-Tidy

    44 (Fedora 44) (Unspecified): Tidy HTML::Mason/Mason components

    2.57-31.fc44: noarch

    Source: perl-Mason-Tidy

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.