-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
>
> 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.
>
yep
I ended up in using the make-dist script (I backported from svn) and
it's the only way to build synce-gvfs from an arbitrary gvfs tarball
a little issue is that actually I need to depend on that *exact*
version of gnome-gvfs... that's too bad, because multiple packages can
pull in different versions of gnome-gvfs... causing troubles when
trying to upgrade a system.
so I decided to put a depend on >=gnome-base/gvfs-${gvfs_V} [1] which
will pull at-least that version of gvfs, but still allow further
upgrades of gvfs.
eventually, package upgrades will pull a newer version of gvfs... in
that case I only hope that things will not break with future versions
of gnome-gvfs
you can check the whole ebuild here:
http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-pda/synce-gvfs/synce-gvfs-0.1-r1.ebuild?rev=1.1&view=markup
- --
FF
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklT6OIACgkQV/B5axfzrPu0aQCfVuh+eXntlVh61Dksj1R08wLn
kaoAmgNjb9FjLJjQYp1eY5aziKe9dpFz
=YE1G
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
