Re: interactive installs

[jnemeth%victoria.tc.ca@localhost (John Nemeth)]

On Nov 15,  4:18am, Brook Milligan wrote:
} OBATA Akio writes:
}  > At least, you need put followings to Makefile:
}  > INTERACTIVE_STAGE+=        install
} 
} Yes.  The result of doing that is a message saying
} 
}       Please install manually with:
}       cd ${.CURDIR} && ${MAKE} install
} 
} which in my case is not appropriate.
} 
} One option is to include a clause in mk/install/install.mk that
} parallels the similar clause in mk/fetch/fetch.mk to enable
} ${INSTALL_MESSAGE} to be written instead of the one above.
} 
} If that existed I could, for example, create an appropriate make
} target in the package Makefile and instruct the user via
} ${INSTALL_MESSAGE} how they should respond to the prompts for
} everything to be installed in a way that pkgsrc will like.  Somehow
} this seems like a hack, but perhaps it is the only way.
} 
} Is this a useful direction?  Are there better ones?  Regardless, is it
} a good idea to modify mk/install/install.mk in this way?  during a
} freeze?

     Absolutely not!  One of the main rules of a freeze is that you
don't modify the infrastructure, and anything under mk is part of the
infrastructure.

} Thanks for any ideas and suggestions.

     The obvious is to figure out what the graphical installer does,
use patching and/or SUBST to do the equivalent, then patch to prevent
the graphical installer from running.

}-- End of excerpt from Brook Milligan