Bug 1004376

Summary: Please drop optional test buildreqs when bootstrapping
Product: [Fedora] Fedora Reporter: Paul Howarth <paul>
Component: perl-Capture-TinyAssignee: Petr Šabata <psabata>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: perl-devel, psabata
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-Capture-Tiny-0.22-4.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-05 15:39:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Howarth 2013-09-04 13:59:58 UTC 
I've just run my build-order script for the first time after the 5.18 rebuild, and came up with some build dependency cycles, such as:

perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Parse-RecDescent->perl-Module-Build->perl-Perl-OSType

perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Parse-RecDescent->perl-Test-Pod

perl-Perl-OSType->perl-Capture-Tiny->perl-Parse-RecDescent->perl-Module-Build->perl-Perl-OSType

perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Parse-RecDescent->perl-Test-Pod

perl-Test-Warn->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Parse-RecDescent->perl-Test-Warn

perl-Tree-DAG_Node->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Parse-RecDescent->perl-Test-Warn->perl-Tree-DAG_Node

perl-Test-Warn->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Test-Warn

perl-Tree-DAG_Node->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Test-Warn->perl-Tree-DAG_Node

perl-Test-Warn->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Parse-RecDescent->perl-Test-Warn

perl-Tree-DAG_Node->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Parse-RecDescent->perl-Test-Warn->perl-Tree-DAG_Node

perl-Test-Warn->perl-Sub-Uplevel->perl-Test-Script->perl-IPC-Run3->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Parse-RecDescent->perl-Test-Warn

perl-Test-Warn->perl-Sub-Uplevel->perl-Test-Script->perl-IPC-Run3->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Inline->perl-Test-Warn

perl-Test-Warn->perl-Sub-Uplevel->perl-Test-Script->perl-IPC-Run3->perl-Test-Pod->perl-Module-Build->perl-Perl-OSType->perl-Capture-Tiny->perl-Parse-RecDescent->perl-Test-Warn

All of these would go away if perl-Capture-Tiny didn't include the optional test buildreqs Inline/Inline::C/Parse::RecDescent when bootstrapping.

It might be argued that all of these cycles involve Module::Build, which, being a dual-lived package, would be available at bootstrap time from the main bootstrapped perl package, but I'd prefer to avoid making special cases for such things where possible.
Comment 1 Petr Šabata 2013-09-05 15:25:59 UTC 
I'm fine with that.  It will be simpler.