installation thoughts

Your thoughts are solicited.

I am working through the installer, and my current plan is to have two
installers: one standalone with everything, and one web-based one (so you
only download what you need).

So I am trying to figure out what installation packages we want/need, and
how to link them together.

Right now, I have the following sketched out, not in stone at all.

Installation Packages
	* Documentation
	* Test files
	* All-static builds (68K, PPC, FAT?)
	* All-dynamic builds (PPC) (default?)
	* All-static builds (68K, PPC, FAT) with -DDEBUGGING ?
	* All-dynamic builds (PPC) with -DDEBUGGING ?
	* MPW Tool (-DDEBUGGING, static, dynamic ?)

	* SYM files ?
	* Source ?

I am thinking four different main binaries: 68K static, PPC static, FAT
static, and PPC dynamic.  On top of that, I wonder whether or not to
include -DDEBUGGING binaries of each.  On top of that, I wonder if the same
4/8 options should apply to MPW tools.  That would give 16 different
binaries, which I am not really opposed to.  But am I missing something?
Or including something unnecessary?

I have yet to do benchmarking on static vs. dynamic; it may be that static
PPC is unnecessary.  If it doesn't benefit from speed, I might just not do
a static PPC build at all.  Also, if -DDEBUGGING does not cause significant
slowdown, I will just include it by default (it has been included in all
alphas so far).  So that would bring us to just 6 total binaries, app/tool
68K/PPC/FAT.

I figure Shuck should just be FAT, if we can swing it.

And then there is the idea of including the SYM files and the source, so
people can go through the debuggers if they want to.

Thoughts?

-- 
Chris Nandor                      [email protected]    http://pudge.net/
Open Source Development Network    [email protected]     http://osdn.com/