[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Depending on Perl modules
- From: James Olin Oden <joden lee k12 nc us>
- To: RPM Package Manager <rpm-list redhat com>
- Subject: Re: Depending on Perl modules
- Date: Fri, 27 Aug 2004 07:25:01 -0400 (EDT)
On Thu, 26 Aug 2004, Dean wrote:
> If I package a Perl application which depends upon external modules
> should I be checking if the modules have been installed outside of the
> package system or should I just be declaring them as dependencies and
> dying if they are not found?
>
> I know it's possible to not depend on them, have the application install
> easily and let Perl go bang and tell them when the modules are not found
> at run time but this seems a little harsh. While this will allow the
> application to work if they have installed them outside of RPM (via perl
> -MCPAN for example) if it does die due to missing modules it could cause
> a fair bit of confusion.
>
Hi Dean, unless you turn off the autodeps stuff you get the dependencies
automatically generated by perl.req or perldeps.pl (pick your poisen) can
parse your scripts correctly.
As an interesting excercise, take perl.req (lives in /usr/lib/rpm) and
run one of your scripts through it:
perl.req yourscript.pl
And then there is a perl.prov for provides. Finally you can do the same
thing with newer versions of rpm with perldeps.pl you just have to throw
a --provides or --requires switch on the command line.
Cheers...james
> Dean
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]