On Fri, 2006-01-06 at 13:52 -0500, Chris Shoemaker wrote: > gog-renderer-cairo.h seems to have escaped the goffice import even though > gog-renderer-cairo.c is present. > > This breaks `make dist'. I can import this file from goffice myself, > and obviously, `make dist' doesn't really care what I put there, but I > don't understand the overall integration policy well enough to know if > it's important that I commit the version that goes with the rest of > goffice or if the most recent version is fine. > > What are our integration and dependency policies for in-tree libraries?
I don't think we have formal policies around this, just common sense. Part of the reason to revise those copies was to make them as-close to the real things as possible. Reviewing the goffice-0.0.4.tar.bz2 file I used as source for the import, *it* doesn't have that file. Huh. I'm tracking it down presently. Come to think of it, I've never enabled cairo on the goffice sub-build, so I don't know if it works or breaks; since cairo was just emerged on my system yesterday, I'll give it a try... -- ...jsled http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
