Upstream software project

perl-Path-Class

Cross-platform path specification manipulation

About perl-Path-Class

Cross-platform path specification manipulation

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

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

Project identity

Project
perl-Path-Class
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6, opensuse-leap-16-0
License expression
Artistic-1.0 or GPL-1.0+
Source repository
Not reported

Source-reported description

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

'Path::Class' is a module for manipulation of file and directory specifications (strings describing their locations, like ''/home/ken/foo.txt'' or ''C:\Windows\Foo.txt'') in a cross-platform manner. It supports pretty much every platform Perl runs on, including Unix, Windows, Mac, VMS, Epoc, Cygwin, OS/2, and NetWare. The well-known module File::Spec also provides this service, but it's sort of awkward to use well, so people sometimes avoid it, or use it in a way that won't actually work properly on platforms significantly different than the ones they've tested their code on. In fact, 'Path::Class' uses 'File::Spec' internally, wrapping all the unsightly details so you can concentrate on your application code. Whereas 'File::Spec' provides functions for some common path manipulations, 'Path::Class' provides an object-oriented model of the world of path specifications and their underlying semantics. 'File::Spec' doesn't create any objects, and its classes represent the different ways in which paths must be manipulated on various platforms (not a very intuitive concept). 'Path::Class' creates objects representing files and directories, and provides methods that relate them to each other. For instance, the following 'File::Spec' code: my $absolute = File::Spec->file_name_is_absolute( File::Spec->catfile( @dirs, $file ) ); can be written using 'Path::Class' as my $absolute = Path::Class::File->new( @dirs, $file )->is_absolute; or even as my $absolute = file( @dirs, $file )->is_absolute; Similar readability improvements should happen all over the place when using 'Path::Class'. Using 'Path::Class' can help solve real problems in your code too - for instance, how many people actually take the "volume" (like 'C:' on Windows) into account when writing 'File::Spec'-using code? I thought not. But if you use 'Path::Class', your file and directory objects will know what volumes they refer to and do the right thing. The guts of the 'Path::Class' code live in the Path::Class::File and Path::Class::Dir modules, so please see those modules' documentation for more details about how to use them.

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 perl-Path-Class

    leap-15.6 (openSUSE Leap 15.6) (Development/Libraries/Perl): Cross-platform path specification manipulation

    0.37-1.23: noarch

    Source: perl-Path-Class

openSUSE Leap 16.0

  1. Package perl-Path-Class

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/Perl): Cross-platform path specification manipulation

    0.37-160000.2.2: noarch

    Source: perl-Path-Class

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.