| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] rpm and perl and packaging question |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Tue, 30 Jul 2013 19:19:08 -0400 (EDT) |
| Cc: | Mark Goodwin <mgoodwin@xxxxxxxxxx>, PCP Mailing List <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <51F84209.5060105@xxxxxxxxxxxxxxxx> |
| References: | <51F767EB.3060008@xxxxxxxxxxxxxxxx> <51F76B91.5070306@xxxxxxxxxx> <51F84209.5060105@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | iNMlOrimqXqboSco3oDQ1kmYAHZi7A== |
| Thread-topic: | rpm and perl and packaging question |
----- Original Message -----
> On 30/07/13 17:30, Mark Goodwin wrote:
>
> > exclude pcp-import-sheet2pcp in the pcp spec, as above.
>
> I'm looking for Plan B here. If RH and friends want to get out of the
> Perl repackaging business, then they should provide more support for
> over-riding the default Requires: generation in an rpm build for perl
> modules.
%if "%{_vendor}" != "redhat"
... could be a simple option. There's similar trickery in pcp.spec.in
for some of the build dependencies.
Mainly cos I don't know the answers to the other rpm-guru questions. :)
cheers.
--
Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: release prep, pmdagfs2, pmcd backtracing, Nathan Scott |
|---|---|
| Next by Date: | Re: rpm and perl and packaging question, Frank Ch. Eigler |
| Previous by Thread: | Re: [pcp] rpm and perl and packaging question, Ken McDonell |
| Next by Thread: | Re: rpm and perl and packaging question, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |