Re: [jokosher-devel] New runscript

["Stuart Langridge" <sil kryogenix org>]

On 11/12/06, Khusro Jaleel <kerneljack gmail com> wrote:
> After I installed those and re-ran the script, it went further and
> eventually after a few minutes I saw it crashed again. Basically the first
> configure failed because of missing 'bison', so the script moved on to the
> next package which perhaps it shouldn't do?
...
> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
...
> checking for LIBOIL... configure: error: liboil-0.3.6 or later is required

> At that point I pressed CTRL+C and stopped it. I'm sure I can manually find
> and fix these missing packages, but I won't, instead I think it's better I
> keep reporting these to you until your script works first time :-) I suppose
> to help first timers, it should identify all these dependencies and make the
> user install them, or is that too complicated a goal? I'm on Ubuntu Edgy
> btw.

The problem is that detecting those packages is hard. I'm not sure how
to do it. The configure script does it by basically writing a tiny C
program that uses them; I really do not want to reimplement autoconf
inside my script if I can avoid it. I currently have two plans:

1. Tell people "before you run the script, run this command", which
will be a command to get all the dependencies (like we have on
http://jokosher.python-hosting.com/wiki/InstallingCvsGstreamer). The
command will differ depending on which Linux distro you are using
2. Have the script detect the compile-time dependencies and tell you
about them, in the same way as it detects runtime dependencies like
pygtk. This is better, but I don't know how to do it. Suggestions?

sil

--
If cryptography is outlawed, only outlaws wifo4(F9%!98f3((hg$;'da"d;f+