rpms/perl-Readonly/devel perl-Readonly.spec,1.2,1.3

[Chris Weyl]

On 10/5/06, Michael Schwendt <bugs.michael at gmx.net> wrote:
> On Thu, 5 Oct 2006 14:52:25 -0700, Chris Weyl wrote:
>
> > On 10/4/06, Ville Skyttä wrote:
> > > On Wed, 2006-10-04 at 18:26 -0700, Chris Weyl wrote:
> > >
> > > >  %changelog
> > > > +* Wed Oct 04 2006 Chris Weyl <cweyl at alumni.drew.edu> 1.03-6
> > > > +- add explict requires on perl(Readonly::XS).  perl(Readonly::XS) is available
> > > > +  for all architectures fedora supports, so there's no good reason to not
> > > > +  require it.
> > >
> > > Hm... except maybe that there's now a build dependency loop,
> > > perl-ReadOnly-XS BuildRequires perl-ReadOnly.
> >
> > Almost...  perl-Readonly requires (not buildrequires)
> > perl(Readonly::XS), whereas perl-Readonly-XS requires and
> > buildrequires perl(Readonly).  So long as perl-Readonly is built and
> > in the repos before perl-Readonly-XS is queued, and perl-Readonly-XS
> > is available before someone tries to install perl-Readonly, we're
> > good....  right?
>
> Still a loop, or what am I missing? Assume you start from scratch:
>
> 1. rpmbuild perl-Readonly  =>  works
>
> 2. rpmbuild perl-Readonly-XS  =>  needs BuildRequires perl-Readonly,
> which in turn Requires perl-Readonly-XS, which hasn't been built yet
>  => *boom*

Ah.  Nice :)

Ok, on examination, perl-Readonly-XS doesn't strictly buildrequires
perl-Readonly, so I've dropped that BR and patched the Makefile.PL to
not complain.  That should cut the loop.

                  -Chris

-- 
Chris Weyl
Ex astris, scientia