[Bug 924938] wrong provides in latest build

bugzilla at redhat.com bugzilla at redhat.com
Mon Mar 25 11:05:08 UTC 2013


Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=924938

--- Comment #27 from Jan Kaluža <jkaluza at redhat.com> ---
> > The question is,
> > what is the difference between Perl Module and Perl Script except the
> > possible extension?
> The file name extension is the #1 distinction criterion. Additional ones are
> the shebang and yet another one is "executable-permissions".

Right, but only the shebang is acceptable for File. It does not detect files
according to names or permissions. But I agree that RPM should start by
checking the extension in this case.

> However, there is a difference between the general case of guessing on a
> file's type and on processing a specific file in context of rpm and
> perl-modules (c.f. the next sentence)

+1

> > Can Perl file with shebang contain Perl Module?
> rpm-relevant perl-modules *must* be on the search-path provided through 
> "@INC" (cf. perl -V) and *must* be named '*.pm' (cf. man perlmod).
>
> Though, I am not aware about perl prohibiting them to carry shebangs or
> these file to carry executable permission, they usually don't have either.

Ok, I will check some Perl files I have here to be really sure and detect
anything with Perl shebang as "Perl script" in next File build.

> Files named *.pl (such as the perl5db.pl case, here), however never are
> modules and therefore should never provide rpm perl()-provides.

As explained above, this should be handled by rpm, not by File. File detects
the type of file according to its content. It will still says "Perl module" for
.pl file if it does not have shebang and defines "package".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6Dph02r6a1&a=cc_unsubscribe


More information about the perl-devel mailing list