On Tue, 21 Mar 2006 05:24:23 +0100, Carlo Calica <[EMAIL PROTECTED]> wrote:
On 3/20/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
>
> Ok, I'm convinced that at the very least it is a decent stopgap
> solution. Any other opinions on that before committing?
>
How long will you wait for opinions? ;)
btw. I got the idea for the configure options feature from the '--'
option
to CompileProgram. So the functionallity is already there in other parts
of the compilation package.
I'm for it. A few things. Need to flag a build as customized.
Either an addition to the version or a file in Resources. Also, an
option to run "configure --help" would be nice.
How would one do that? Change the version directory or place a string in a
text file in the installation directory?
Why would it have to be marked as customized? One is left to the whims of
the recipe author anyways and the program will be configured after his/her
wishes, which doesn't have to be optimal. At the same time, if I change
configure options in the recipe, there's no way to see that the program is
a custom build.
I think that the option should be in because anyhow I will need to change
the configure options for some programs and this saves the effort to
download the recipe, move it and then edit it before Compile.
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
