0.11 ebuilds

[Iain Buchanan]

Hi,

Attached are some preliminary ebuilds for 0.11 for your perusal and
inclusion! They're not all here, just some main (IMHO) ones:

synce-librapi2-0.11.ebuild
synce-gnome-0.11.ebuild
synce-libsynce-0.11.ebuild
synce-librra-0.11.ebuild
synce-sync-engine-0.11.ebuild
synce-gnomevfs-0.11.ebuild
synce-odccm-0.11.ebuild

the others I may get to soon...

Some questions arose though, they're not all gentoo specific:

general:
* do various packages still have the dependency on check? I
couldn't find check.h or libcheck anywhere in the source for
librapi2 for example.
* (gentoo) should librapi2, libsynce, etc go into app-pda or
dev-libs? It's been in app-pda in the past, but maybe dev-libs
is more appropriate?
* (gentoo) why are packages prefixed with synce- (synce-librapi,
synce-libsynce)? Why not just the packaged name as per the
sourceforge download?

odccm
* why is there a dbus dependency in 0.10.0-r1 but not in 9999?

librra
* (Gentoo) how do I handle the name change from rra to librra?
For now I've just ! synce-rra in DEPEND.

thanks,

[Iain Buchanan]

Post by Iain Buchanan
Hi,
Attached are some preliminary ebuilds for 0.11 for your perusal and

Sorry for rushing that out, but I wasn't sure if I would get online for
a couple of days, yet here I am, back already :)

These are of course not very well tested yet. I stuffed up
synce-sync-engine but you can fix it by manually installing the correct
plugin.

I just tested syncing contacts, and it's working as well as ever!

thanks,

[Vasco Steinmetz]

Post by Iain Buchanan
Attached are some preliminary ebuilds for 0.11 for your perusal and

Did you add the changes to the -9999 ebuilds as well?

Just patched my working copy's gnome ebuild to make it install again.
Saw you added !app-pda/synce-rra to app-pda/synce-librra too.

Are there any other changes, that should make it into the -999 SVN ebuilds too?
Or are the changes not simply not committed, yet?

Your preliminary ebuild show KEYWORDS="~*" instead of KEYWORDS="~x86".


Here's a solution for Sync-Engine's OpenSync plugin installation:

src_install() {
distutils_src_install

insinto /usr/share/${PN}/
doins config.xml

insinto /usr/lib/opensync/python-plugins

if has_version '>=app-pda/libopensync-0.30'; then
newins plugins/synce-opensync-plugin-3x.py synce-opensync-plugin.py
else
newins plugins/synce-opensync-plugin-2x.py synce-opensync-plugin.py
fi
}

The OpenSync plugins should be placed into their own ebuilds though.
There's already a hardmasked (and probably outdated) package named app-pda/libopensync-plugin-synce.


The content of the plugins directory gets installed into /usr/lib/python2.4/site-packages/plugins too.
Is that correct?



Cheers,
Vasco