I could have sworn that sawfish has it's own lib-exec directory for lisp code and compiled modules. I am not currently at my computer so I can only speculate. Have you tried some sort of --lib-exec flag? It is also possible that sawfish is auto-detecting where librep is and installing modules into librep's libexec directory.
This does raise the question, how would we want sawfish to interact with librep? Should it be a set of modules and lisp code that is installed into a librep system (the sawfish executable being a "#!/usr/bin/rep" script) or is it a separate program that embeds librep? On Dec 20, 2007 8:10 AM, Andrea Vettorello <[EMAIL PROTECTED]> wrote: > I want to install a second Sawfish instance in /usr/local to modify > and break freely, but even if i specifically declare at configuration > time the --prefix and --exec-prefix variables with my path, there's > always an error when it tries to overwrite the client.so lib under > /usr/lib/rep/i486-pc-linux-gnu/sawfish/ (and not installing in > /usr/local). > > As i don't know autotools, am i missing something trivial? Is this the > expected behaviour or are autoconf scripts broken? > Should i install librep from source too (in /usr/local) and pass this > one at config time? > > > -- > Andrea >
