On Thu, 10 Apr 2008, Mark Glines via RT wrote:
> On Thu Apr 10 14:16:58 2008, infinoid wrote:
> > Oddly, adding config/auto/macports.pm to MANIFEST didn't help. It is
> > copied, but I don't think this module is getting "use"'d, for whatever
> > reason.
>
> What the heck? When I added t/steps/auto_macports-*.t to MANIFEST (in
> r26916), it started working.
Yes. The fact that lib/Parrot/Configure/Step.pm lists auto::macports
implicity *assumes* that there will be corresponding tests in
t/steps/auto_macports-*.t, and if there aren't, Configure bails out with
a fatal error during build time.
This is just really strange. For example, it makes it more difficult
to develop a new step because you can't even begin to develop the new
step unless you already have the tests in place.
> So, uh, fixed in r26916 and r26914. Though I have no idea why r26916
> fixed it and r26914 didn't.
Well, adding those tests works around the design oddity, but I wouldn't
really call it "fixed".
--
Andy Dougherty [EMAIL PROTECTED]
