Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!kth!draken!tut!ra!rosenber
From: rosenber@ra.abo.fi (Robin Rosenberg INF)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Idea for program start-up (long)(ulong)
Summary: Use a makefile
Message-ID: <132@ra.abo.fi>
Date: 18 Jun 89 15:31:35 GMT
References: <0873.AA0873@chroma>
Organization: Abo Academy, Finland
Lines: 62

(LONG)
In message 2266 bryan@chroma.UUCP (Bryan Ford) points out some problems 
with executing programs in the startup-sequence. He points out that adding
something to the s-s. is not trivial and thus effectively prevent programs
from editing it. I think having to edit the startupsequence just to install
a program is a primitive and *BAD* method.

Bryan suggests we use a 'mountlist' to install programs. I suggest a
'make-file' instad.
Why a makefile then? The problem is that sometimes when you are about to
do something you have to do something
else first. For example we cannot do anything that involves dh1: before 
dh1: is mounted. We probably have a lot of thing that is located on dh1:.
A makefile takes care of executing ALL commands we need to execute in the
correct order since we say that to do this you must have done that first. 
Another plus with a makefile is that it is easy to edit, both manually
and automatically (automagically)

> Ideally, this Start program would be an ARP program, and there would be
> routines provided in arp.library which could allow programs to add, change,
> or delete entries in the StartList.

Or in a separate library so the routines don't lie in memory when not needed.
We need them only when booting(maybe) and when installing a program.

> Of course this couldn't be used for some parts of the Startup-Sequence like
> conditionally copying things to RAD: or whatever.  However, it would get
> Startup-Sequences down to size, and it would be great for "normal" users.

A makefile could handle conditions. 
The unix-like make we use for compiling and linking programs is not the best
solution. Rather we should have a tailored format.

ISSUE#2: Setting program parameters.
Programs that have parameters to change should have an intuition program to
to that. The program should be callable from the main preferences program
so we can set *all* parameters from essentially the same place. The preferences
program could store the parameters in the makefile along with the rules
for running the program. 

	SetMap:
		PAR keymap = s
		CMD sys:system/setmap <keymap>

Comments?

> !Have fun!
>				Bryan

Don't worry, be happy!

	Robin

------               o
Robin Rosenberg, cs. Abo Akademi - FINLAND
"I don't speak for anyone but me"

PS! I tried a lousy idea. I changed my startup-sequence to read
	lmk -f s:boot-makefile
	endcli
    And then a makefile takes care of running all commands in the
    correct order. Pretty nice.