> > > > > Free Software means never having to say "now what do I do" when your closed > source vendor goes belly up. > > > A "dummies guide to gEDA" would be nice but a lot of the problem is > related to the flexible nature of linux. > With that other OS where you know exactly what is available in the user > enviroment but in linux you have no > idea if the user's distro has the needed libs or not.
It is necessary to write: a) What are the gEDA's requirements on the system b) How do I test if my system fullfills them (step-by-step guide) c) How do I convert non-compliant system into a compliant one (step-by-step guide) d) How do I install gEDA on compliant system (step-by-step guide) e) Where to report bugs when some of the step-by-step guides doesn't work. With these informations provided to user, installing gEDA will unconditionally work. Write in human brain code, not philosophical essays. Ronja is written in human brain code (it's even transaction oriented - there is a box you read where the step is described, then you hit box boundary, commit the transaction, cross the box on printout with a pencil and move over to another. This prevents execution of half the box) and it works well. > Locating,downloading and installing a bunch of different > programs is daunting for a end user. One solution would be to simply When there's a step-by-step guide, it isn't daunting, because the user even doesn't have to think about what he's doing. Cl<
