GnuCash 2.1.1 binary and QT support
Nathan Buchanan
nbinont at gmail.com
Sat May 12 02:42:12 EDT 2007
Hi Andreas!
On 5/9/07, Andreas Köhler <andi5.py at gmx.net> wrote:
>
> Hi Nathan,
>
> regarding http://bugzilla.gnome.org/show_bug.cgi?id=435928, I wonder
> whether the distributed GnuCash 2.1.1 binary setup lacks the qt3-wizard
> for AqBanking. This may be due to a missing rebuild of AqBanking,
> because I think otherwise you would have needed to actively block QT or
> install.sh would have failed. Currently there is no mechanism to let
> install.sh automagically rebuild single libraries whose instructions
> changed since the last build. There are several difficulties involved:
>
> * we do not track revisions of instruction sets
> * it is not trivial to determine what packages have to be rebuild even
> if we did, given
> - dependencies
> - customizations
> - mixtures of revisions used to build libs
> * the user might not know better
> * the risk to trash valuable data
> * maybe more...
Yes, this is exactly what happened - I didn't rebuild everything, and missed
this one (hopefully it was the only one).
My question is how we could avoid that. I do imagine one or a
> combination of
>
> * I make a list of libs that definitely need to be rebuilt because of
> changes between release A and A+1
> * You make that list by looking at the changes
I like a combination of these first two...my only question would be how I
would identify a change that requires a rebuild. You mention it's not all
that simple. I'll catch you on irc sometime to chat about this, if you don't
mind. This is a bit of a learning process for me. I appreciate your help :)
* You rebuild from scratch
In the meantime, I'll use this approach.
If you have an idea how we can improve this build and release process,
> just let me/us know :-)
> Yours,
> -- andi5
>
Thanks,
Nathan
More information about the gnucash-devel
mailing list