[Bug 234861] Review Request: perl-Mail-Transport-Dbx - Parse Outlook Express mailboxe

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: perl-Mail-Transport-Dbx - Parse Outlook Express mailboxe


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234861





------- Additional Comments From rc040203 at freenet.de  2007-04-05 03:21 EST -------
(In reply to comment #5)
> (In reply to comment #4)

>   What my basic question is towards perl-* packages/its packaging is that in
> most of normal packages that uses gcc compilation uses ./configure
These are configuration-time options (If "found" then "activate/build-in a feature")

> and from
> there also we can know if we are missing to add any packages as BRs. But I am
> not able to find same for perl packages. Instead I saw "make test" is the only
> one way to satisfy package's all requires Build time dependencies.
... and these are run-time options (run-time of the test-suites)

The former rarely exist for perl-packages (Nevertheless, they occasionally they
exist), while the latter also occasionally exist for "ordinary packages" (but
most packages don't ship a testsuite)

The problems actually are:
* rpm doesn't destinguish between both situations.
* Most packages do not properly destinguish between both cases.

In practice, packagers have to resort to a "compromise that works", which in
most cases will be "activate a testsuite only if it doesn't pull in additional
configuration-time deps".

In most cases, such as most perl-packages, "activating the testsuite" will not
have negative impacts on package deps, but that's an item to be carefully
watched for.



-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.