Christian Stimming <christ...@cstimming.de> writes:
> Yes, we have that for most dependencies: We check by pkg-config --atleast-
> version, which reliably builds the dependencies anew if we upgraded the
> version number.
>
> We don't clean up all of the dependency installation directories, though,
> which caused the unnecessary big setup package. I don't see much problem in
> that, though, and thus wouldn't invest extra developement time in any
> automatic mechanism here.
And also caused the issue where we stopped including a dependency in the
new build but it was already there in the daily build. I don't know if
we should fix this in an automated way or not..
> Christian
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warl...@mit.edu PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
