Hi Stuart,
[snip]
>* Where does it put the .sos? Into the system's /usr hierarchy, or
>into the user's ${HOME}/geda-sources (or whatever) hierarchy?
It throws everything into $HOME/geda. The .so files go into
$HOME/geda/lib.
>* Does it check for each package before building and installing it?
Not yet. I have to add this actually. Also, I tried this script
on my Debian box and it didn't work because standalone libiconv confused
glib a little. I need to fix this.
>Also, how about different versions of the same package? That is, if I
>have GTK-2.4.X on my machine, does it build and install GTK-2.6.X, or
>does it just leave well enough alone?
It installs gtk+ 2.6.x into $HOME/geda which can happily coexist
with which ever gtk+ is install in the system. This is the beauty of prefix
installs, the whole directory is self contained and mostly doesn't depend or
interfere with anything else. I really wanted to install the dependencies
unconditionally (even though I can't do that with libiconv and a few of
the others) to minimize the effects of something external being slightly
different and breaking the build.
>
>* Does it require you to be root?
Nope!
>
>* How easy would it be to extend to install other packages, like
>those required for stuff in the gEDA Suite, but not in gEDA/gaf?
Easily done.
>
>I suppose I could look at the code, but it's easier to ask . . . .
>
>Thank you again! I look forward to incorporating this!
Yeah, I'm not yet convinced that it should be incorporated, but
it would hopefully solve some of the rather more bizarre problems people
keep running into. Most people can install gEDA using standard mechanisms
because they have a modern working system. Let's talk some more about
this on Thursday.
-Ales
