On Sun, Sep 02, 2007 at 12:32:09PM -0400, Simon Ruggier wrote:
> On 9/2/07, Chris Frey <[EMAIL PROTECTED]> wrote:
> > It can be automated with a script, and I could drop a "build-all" style
> > script in the root directory if this is a major problem.
>
> How about building them conditionally with a configure flag like
> --enable-opensync?
Well, one of the issues you'll have to overcome is that I do like the
build system the way it is. :-)
I don't see a major advantage to putting it all together into one,
besides the simple part of typing configure / make a few more times.
That can be scripted easily.
The advantage to keeping them separate is that they can be split into
separate source tarballs someday if needed. Not that it's likely, but
might be handy someday.
Are there real advantages to having things in one configure setup?
I don't think I'd change the build process if it is just an aesthetics thing.
One thing we do need, though, is a binary package for the opensync plugin,
so I am interested in that.
If you do decide to convert things, I'd like to keep the behaviour we
have now. Specifically:
- the plugin and gui are each enabled / disabled separately
- if disabled, their dependencies are not required for build,
and won't stop the build
- keep the configure scripts relatively simple and straightforward
(this is a challenge)
- Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
