Re: sysinst split project - The Configuration File

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

On 07.02.10 22:12, David Holland wrote:
> (from a while back)
> 
> On Wed, Dec 16, 2009 at 06:19:53PM -0200, Silas Silva wrote:
>  > On Wed, Dec 16, 2009 at 03:12:07PM +0000, David Holland wrote:
>  > > It seems to me that there are at least three different questions here.
>  > > [...]
>  > > The second is: whether it should be possible to direct the overall
>  > > progress of the install process using a user-supplied script, which
>  > > e.g. plugs together components of sysinst and executes them.
>  > 
>  > I think I didn't got it right (mainly because of my poor English
>  > understatement :-[), but what you mean here? That people will call
>  > sysinst functions (components?) to achieve something?
> 
> It is a push/pull issue, basically.
> 
> The way sysinst works right now, you start it, and from time to time
> it asks the user questions.
> 
> One way to automate this is to set it up so you start it, and from
> time to time it calls hooks in the sysinst automation script to ask
> questions; the script figures out the answer and returns control.
> 
> The other way is to set it up so you start the automation script, and
> it calls into sysinst to do stuff, telling sysinst exactly what to do,
> and sysinst never calls back to ask questions because the answers have
> been passed to it already.
> 
> Since programming with callbacks is usually troublesome, the second
> architecture is probably preferable, as long as it doesn't become
> insanely complicated or make the automation script into a large piece
> of boilerplate that one customizes by making tiny edits in exactly the
> right places.

I'm looking forward to being able to run automated network installs.

Christoph