On Thu, Dec 30, 2004 at 09:26:33PM +1100, John Sheahan wrote: > Karel Kulhavy wrote: > > > > > >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) > > surely in the general case option (c) is hard to write.
Why? If we depend on libraries L1 and L2, we just supply a pointer to L1 homepage where step-by-step guide how to install L1 is, and a pointer to L2 homepage where step-by-step guide how to install L2 is. > Getting a slackware 1.0 system to be 'compliant' would be a hard > document to write and debug. You can make Slackware system be compliant the same way as you do any other system - download, compile, install. > > Perhaps a list of systems install is tested/not hard on would be more > practical. This is like writing driving code by listing all known road crossings in the country and writing which road has the priority on that particular crossing. Or you could write that for "only the most frequented crossings" which yields enormous death tolls on the not-so-frequented crossings. Cl<
