On 1/10/06, Hawkwind <Cliff Wade> <[EMAIL PROTECTED]> wrote:
The issue with using autogen.sh is that you are requiring your users to have a working set of autotools installed.
Sure, most e users currently have this, but given that enlightenment.freedesktop.org supplies tarballs with configure scripts (afaik), and that distros will eventually supply e17 binaries, there are going to be more and more e users who won't be able to build modules without setting up build tools on their systems first (and they may bitch about their problems with that here).
They won't need them if a working configure script is available.
I'm using a configure script in more recent versions of the moon module for this reason - the autogen.sh is there as well though.
Regards!
David
Also, I was under the
impression that all modules on get-e.org had to use ./autogen.sh
instead of ./configure ?
The issue with using autogen.sh is that you are requiring your users to have a working set of autotools installed.
Sure, most e users currently have this, but given that enlightenment.freedesktop.org supplies tarballs with configure scripts (afaik), and that distros will eventually supply e17 binaries, there are going to be more and more e users who won't be able to build modules without setting up build tools on their systems first (and they may bitch about their problems with that here).
They won't need them if a working configure script is available.
Why is evolume the only one that is
different and will this ever change ?
I'm using a configure script in more recent versions of the moon module for this reason - the autogen.sh is there as well though.
David
