Dan Sugalski wrote:
> That's so, but I was thinking something a bit more manual than using
> build_perl.com. Basically take the Magic Config File from some build (or
> roll it yourself) and the appropriate symbols and build a new version of perl.
OK That's the idea behond config.com and Policy.com (particularly the latter
since the former may have some bits that are version dependent).
> >So that the interactive build becomes this two step process?:
> >
> > $ @configure
> > $ mmk dwim
>
> Interactively I'd still do a MMK TEST and MMK INSTALL separately, but
> that's just me.
>
> >Sounds reasonable, except for the fact that I think that if you do:
> >
> > $ @configure
> > $ mmk install
> >
> >the dependencies are such that targets "all" and "test" ought to fall into
> >place - is this not so? I have no time to test that right now....
>
> Nope. MMK INSTALL depends on miniperl, but not all of perl or the modules.
> Go figure...
Yes I think one is supposed to be able to run `make minitest` on unix
to help uncover problems with a bad build or port so that does make
sense. So it's back to a separate .com to satisfy Charles' request...
Peter Prymmer
