pcp
[Top] [All Lists]

Re: [pcp] rpm and perl and packaging question

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: [pcp] rpm and perl and packaging question
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 02 Aug 2013 08:37:10 +1000
Cc: Mark Goodwin <goodwinos@xxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20130801210112.GB32678@xxxxxxxxxx>
References: <51F767EB.3060008@xxxxxxxxxxxxxxxx> <y0mli4nk4za.fsf@xxxxxxxx> <51F9D6B2.6060701@xxxxxxxxxxxxxxxx> <y0mwqo6hyju.fsf@xxxxxxxx> <51F9E2DE.1090005@xxxxxxxxx> <51FAC865.4030304@xxxxxxxxxxxxxxxx> <20130801210112.GB32678@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
On 02/08/13 07:01, Frank Ch. Eigler wrote:
... Getting the Spreadsheet::Read package into Fedora is
another possibility; there's just some process involved.  Another
solution could be to change pcp-import-sheet2pcp to rely on a more
commonly distributed package.

nod ... but someone has to sign up for the work in either case.

The problem also seems to be unique to RH/Fedora as we don't see it on
the other platforms that PCP installs on.  [...]

Do those other platforms distribute the Spreadsheet::* suite?  Or do
they let the soft-dependency break upon usage?  These would benefit
from your use -> require and warn change too then.

It varies. All of the Debian derivatives and SuSE include the perl module in their package repositories. For most of the others you need to talk to cpan for _many_ of the pcp perl dependencies, not just Spreadsheet::Read. This is from memory (a big risk right there), as it is something I need to do once and then forget on each of my QA machines.

<Prev in Thread] Current Thread [Next in Thread>