On Mon, 2008-12-22 at 23:18 +0100, Mark Ellis wrote: > On Mon, 2008-12-22 at 20:56 +0100, Adam Williamson wrote: > > On Mon, 2008-12-22 at 20:50 +0100, Federico Ferri wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > hi, > > > > > > why synce-gvfs requires a _built_ src tree of gvfs? > > > can't just rely on the gvfs src tree? > > > or otherwise could the gvfs install some specific files which expose > > > its api and its build output to the other apps needing it? >
I knew I'd seen something else somewhere. Federico, there's an attachment in the patches section of the sourceforge tracker regarding gvfs, I don't know if it's useful to you. > gvfs has no public interfaces. There have been a number of requests on > the gvfs list for such a beast, including mine. The current response > from the devs is that this may happen, but no guarantees. > > synce-gvfs requires a built tree because the internal build structure of > gvfs also changes sometimes, and I don't have the time to follow it > every time this happens, whereas with a built tree we can get by with > the internal headers and the libdaemon library (and I have to fiddle > even this sometimes). > > The crappy workaround I came up with was the stuff in the make-dist dir > in the synce-gvfs source, which will grab everything it needs from an > unbuilt gvfs source tree and allow you to build a self contained > synce-gvfs source. This is the method used to produce the current > synce-gvfs tarball. Yes this is broken with gvfs 1.0.2. I overcame this > for ubuntu by rebuilding the source against a 1.0.2 tree and including > this synce-gvfs tree in the ubuntu package. > > > > > > > actually, making a synce-gvfs package for gentoo turns out to be too > > > messy, and current pkg is somewhat broken. > > > > I did it for Mandriva by simply including a gvfs tarball as a source in > > the synce-gvfs package. It's messy, but it works. > > -- > > Yeah, that's a pretty good workaround Adam, messy but we don't have much > choice. > > I'm arranging for a new synce release in January, there will be a new > gvfs source created against 1.0.2, but this situation is not going away > as far as I can see. > > If anyone has any suggestions I'm all ears. > > Mark >
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------
_______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
