On Mon, Jun 27, 2011 at 7:28 PM, Marcela Maslanova <mmasl...@redhat.com> wrote:
> Hello list,
> you might notice that rebuild stopped for a while. I run out of packages,
> which had "normal" dependencies. Now I have a list of cyclic dependencies,
> which are dependent back and forth.
> Because we'll be doing mass rebuild every year, I'd like to use bootstrap
> macro, which could help us little.
> You can see example in perl-HTTP-Lite. There were dependencies for test suite
> like Test::Pod.
>
> The macro perl_bootstrap is actually set to 1. After rebuild will be done, it
> will be switched to 0. So, now are marked buildrequires or test suites
> switched off. I'd like to use it at least in packages, which caused major
> problems. Please note that it doesn't broke your specfiles in EPEL.
>
> Example:
> BuildArch: noarch
> BuildRequires: perl(ExtUtils::MakeMaker)
> %if !%{defined perl_bootstrap}
> BuildRequires: perl(Test::CPAN::Meta)
> BuildRequires: perl(Test::MinimumVersion)
> BuildRequires: perl(Test::Pod)
> %endif
> Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo
> $version))
>
> %{?perl_default_filter}
> ...
> %check
> # most real tests require network access - ignore "skipping test on this
> # platform" messages
> %if !%{defined perl_bootstrap}
> RELEASE_TESTING=1 make test
> %endif
> ...
Marcela,
I think that when using perl_bootstrap macro in this way, it would
also be useful to make the necessary info available in repository
metadata so that we can easily find these bootstrappable packages in
future (to rebuild without bootstrap) and to know which of their
dependencies are soft. Maybe in your example we could also
Provides: perl-bootstrap(Test::CPAN::Meta)
Provides: perl-bootstrap(Test::MinimumVersion)
Provides: perl-bootstrap(Test::Pod)
--
Iain.
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
