On Monday 10 December 2007, Marc Espie wrote:
> On Sun, Dec 09, 2007 at 06:41:49PM -0800, J.C. Roberts wrote:
> > Assuming you're going to do something like this:
> >
> > EXDIR= ${PREFIX}/share/examples/${????}
> >
> > pre-fake:
> > ${INSTALL_DATA_DIR} ${EXDIR}
> > ${INSTALL_DATA} ${WRKSRC}/README ${EXDIR}
> > ${INSTALL_SCRIPT} ${WRKSRC}/example/*.pl ${EXDIR}
>
> That's not the intended usage of pre-fake.
>
> pre-fake has very little applicability, you'll see it used quite
> seldom.
>
> Normal `fake' installs use pre-install, do-install, post-install.
>
> pre-fake is a hook that's specifically there to setup some stuff that
> fake will need.
>
> And you really don't want to know when that's needed.
Thanks Marc for the clarification.
I mistakenly picked pre-fake since I wanted to be sure that after
running `make fake` I could then run `make update-plist` without
missing anything.
I got confused by the use of the term "install" in the pre-install,
do-install and post-install targets, since the names imply they are
hooks (chronologically) around `make install` --which would be too late
to update the plist since the package would already be (re)built.
As always, the bsd.port.mk man page has the details spelled out
perfectly, "See the description of THE FAKE FRAMEWORK for the
non-intuitive details of the way {pre,do,post}-install hooks are
actually used by the ports tree."
Thanks again,
JCR
