Bug 4015 - [review] rpmbuild find perl(DBI) as requirement
Summary: [review] rpmbuild find perl(DBI) as requirement
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Building & Packaging (show other bugs)
Version: 3.0.1
Hardware: Other other
: P5 normal
Target Milestone: 3.0.2
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-03 07:46 UTC by Theo Van Dinter
Modified: 2004-12-15 07:05 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
suggested patch patch None Theo Van Dinter [HasCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Theo Van Dinter 2004-12-03 07:46:40 UTC 
error: Failed dependencies:
        perl(DBI) is needed by perl-Mail-SpamAssassin-3.0.1-1
Comment 1 Malte S. Stretz 2004-12-04 12:17:02 UTC 
... what's the bug?  I have no clue about RPMs but if it's about the spec 
file, I'd say it falls under trivial fixes.
Comment 2 Theo Van Dinter 2004-12-04 13:42:12 UTC 
Subject: Re:  rpmbuild find perl(DBI) as requirement

On Sat, Dec 04, 2004 at 12:17:03PM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> ... what's the bug?  I have no clue about RPMs but if it's about the spec 
> file, I'd say it falls under trivial fixes. 

I haven't quite figured out if it's a bug or not.

In short, when building, perl(DBI) is found as required by one of our modules,
which it is.  The issue is that our module is optional and not used by
default.

So I don't like the fact that DBI is required by RPM, but I understand what
the thinking is behind it.

This brings me to: should the SQL stuff be a separate RPM (don't like that),
or is there a way to force DBI to not be required, or if you want RPM
packaging do you just suck it up and install the DBI module?
Comment 3 Theo Van Dinter 2004-12-09 23:21:10 UTC 
fixed.  r111477
Comment 4 Theo Van Dinter 2004-12-09 23:22:15 UTC 
actually, I'm going to reopen and aim at 3.0.2 ...  it's an issue there too.
Comment 5 Theo Van Dinter 2004-12-09 23:26:01 UTC 
Created attachment 2562 [details]
suggested patch

I verified this worked via:

/usr/lib/rpm/perl.req `find . -name "*.pm"`

from my 3.0 branch WC
Comment 6 Justin Mason 2004-12-13 19:08:33 UTC 
+1
Comment 7 Michael Parker 2004-12-15 12:43:42 UTC 
+1
Comment 8 Daniel Quinlan 2004-12-15 16:05:06 UTC 
applied to 3.0-branch and HEAD, closing as fixed