OpenSUSE SynCE RPM Repository

Discussion:

Tejas Guruswamy

2008-11-25 18:39:11 UTC

Hello everyone,

Over the last few days I have got a semi-official OpenSUSE SynCE RPM
repository set up on the OpenSUSE Build Service at
https://build.opensuse.org/project/show?project=system%3ASynCE. I put a
list of the packages I have building automatically there at the bottom
of this email.

What I wanted to ask is 1) is there anything I am missing?
and 2) for usb-rndis-lite am i correct in saying that it should not be
needed for kernel versions > 2.6.21? except in some cases where it might
be necessary to apply the "samsung" patch?

I will probably send an email out on the synce-users list soon to ask
for testers, users, and collaborators on this project. SynCE is
something openSUSE has not been up-to-date with for some time now, and
it has resulted in many questions to these lists :) hopefully this
should help.

Also available are two One-Click metapackages, synce-kde
(kde{3,4}-kio_rapip + synce-kpm + sync-engine + dependencies) and
synce-gnome (synce-{g,gnome}vfs + synce-trayicon + sync-engine +
dependencies). I will try and make some nice images like openSUSE seems
to have for everything else ...

Package List
dynamite v. 0.1.1
kcemirror v. 0.2
kde3-kio_rapip v. 0.10
kde4-kio_rapip v. 0.1
libmimedir v. 0.5
libopensync-plugin-synce-legacy v. 0.22 (from opensync website, for
WM2003 devices)
librapi v. 0.12
librra v. 0.12
librtfcomp v. 1.1
libsynce v. 0.12
orange v. 0.3.2
synce-gnomevfs v. 0.12
synce-gvfs v. 0.12
synce-hal v. 0.2
synce-kpm v. 0.12
synce-sync-engine v. 0.12
synce-trayicon v. 0.12
unshield v. 0.5.1
usb-rndis-lite v. 0.11 with samsung patch as a KMP

Adam Williamson

2008-11-25 18:58:12 UTC

Permalink

Post by Tejas Guruswamy
What I wanted to ask is 1) is there anything I am missing?
and 2) for usb-rndis-lite am i correct in saying that it should not be
needed for kernel versions > 2.6.21? except in some cases where it might
be necessary to apply the "samsung" patch?

I don't see anything missing. I think it's more like kernel versions >=
2.6.24, but my memory is somewhat hazy. I don't think the WM5+ support
was in the kernel as far back as 2.6.21, though. I'm pretty sure it was
merged later than that.

Post by Tejas Guruswamy
I will probably send an email out on the synce-users list soon to ask
for testers, users, and collaborators on this project. SynCE is
something openSUSE has not been up-to-date with for some time now, and
it has resulted in many questions to these lists :) hopefully this
should help.
Also available are two One-Click metapackages, synce-kde
(kde{3,4}-kio_rapip + synce-kpm + sync-engine + dependencies) and
synce-gnome (synce-{g,gnome}vfs + synce-trayicon + sync-engine +
dependencies). I will try and make some nice images like openSUSE seems
to have for everything else ...

I would suggest you also package (if it's not done already) and include
in these metapackages KitchenSync (for KDE 3) and multisync-gui (for
GNOME). It's a good idea to have a GUI frontend so people don't have to
futz about with msynctool. Get multisync-gui from this SVN repo:

http://svn.opensync.org/multisync/branches/multisync-gui-0.2X

KitchenSync is part of kdepim. For KDE 4 it's a bit of a mess, I haven't
sorted it out yet.

Another thing I do for MDV is have separate meta-packages for WM5+ and
WM2003 devices. You can check out the MDV metapackages at:

http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/task-wm5sync-common/current/
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/task-wm2003sync-common/current/

--
adamw

Tejas Guruswamy

2008-11-26 18:57:52 UTC

Permalink

Thanks for the tips Adam!

Post by Adam Williamson
I don't see anything missing. I think it's more like kernel versions >=
2.6.24, but my memory is somewhat hazy. I don't think the WM5+ support
was in the kernel as far back as 2.6.21, though. I'm pretty sure it was
merged later than that

OK, thanks for the info. Is there any reason to *not* include the
samsung patch with the kernel module? That saves me having two different
packages. TBH there is no need for me to build packages for anything
before openSUSE 10.3 which was kernel version 2.6.22 ... I don't know
how much had been merged by then.

Post by Adam Williamson
I would suggest you also package (if it's not done already) and include
in these metapackages KitchenSync (for KDE 3) and multisync-gui (for
GNOME). It's a good idea to have a GUI frontend so people don't have to
http://svn.opensync.org/multisync/branches/multisync-gui-0.2X

Yup, those programs are part of the openSUSE distro. But its a good idea
to add them into the one-click as suggested packages, thanks.

Post by Adam Williamson
KitchenSync is part of kdepim. For KDE 4 it's a bit of a mess, I haven't
sorted it out yet.

KDE4-kitchensync (working with akonadi etc.) has been under development
- it is scheduled to release with 4.2 but they I think they are holding
it back till opensync 0.40 stable releases. Could be a while :)
The SVN code is out there, haven't tested it personally. It definitely
needs opensync 0.3+.

Post by Adam Williamson
Another thing I do for MDV is have separate meta-packages for WM5+ and
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/task-wm5sync-common/current/
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/task-wm2003sync-common/current/

Thanks, I will take a look at that!

Regards,

Tejas

Adam Williamson

2008-11-26 19:05:33 UTC

Permalink

Post by Tejas Guruswamy
Thanks for the tips Adam!

Er, remind me again about the Samsung patch :)

Post by Tejas Guruswamy
KDE4-kitchensync (working with akonadi etc.) has been under development
- it is scheduled to release with 4.2 but they I think they are holding
it back till opensync 0.40 stable releases. Could be a while :)
The SVN code is out there, haven't tested it personally. It definitely
needs opensync 0.3+.

The thing is, KitchenSync is just a front end, like msynctool. There's
still, AFAIK, no actual opensync 0.3/0.4 plugin for KDEPIM 4. So if you
try to build and use this KitchenSync, you wind up with a setup which
cannot actually sync anything with KDE 4, and you're stuck with opensync
0.3, which isn't much use in a real world setup.

Presumably it can sync other things using any working opensync 0.3
plugin (heh. heh.), but to me, it doesn't seem worth the effort...

--
adamw

Adam Williamson

2008-11-26 19:29:03 UTC

Permalink

Post by Adam Williamson

Post by Tejas Guruswamy
OK, thanks for the info. Is there any reason to *not* include the
samsung patch with the kernel module? That saves me having two different
packages. TBH there is no need for me to build packages for anything
before openSUSE 10.3 which was kernel version 2.6.22 ... I don't know
how much had been merged by then.

Er, remind me again about the Samsung patch :)

jc reminds me that the 'Samsung patch' is what I usually refer to as the
'dirty patch'.

No, AFAIK, there's no reason to separate it out. We haven't yet found
any real-world situation where it causes any regressions.

--
adamw

Tejas Guruswamy

2008-11-27 19:28:16 UTC

Permalink

Post by Adam Williamson
The thing is, KitchenSync is just a front end, like msynctool. There's
still, AFAIK, no actual opensync 0.3/0.4 plugin for KDEPIM 4. So if you
try to build and use this KitchenSync, you wind up with a setup which
cannot actually sync anything with KDE 4, and you're stuck with opensync
0.3, which isn't much use in a real world setup.
Presumably it can sync other things using any working opensync 0.3
plugin (heh. heh.), but to me, it doesn't seem worth the effort...

It (kde4-kitchensync) is actually supposed to include the syncing
framework to sync KDE4 PIM data IIRC. I have no idea how complete it is
though. It now uses akonadi and all kinds of clever fanciness :)

Regards,

Tejas

Adam Williamson

2008-11-27 19:33:48 UTC

Permalink

Post by Tejas Guruswamy

Ah, that I didn't know. I suspect everyone is working away in separate
sealed compartments, here :\. I'll have to test it out.

--
adamw

Dave Williams

2008-12-01 21:54:17 UTC

Permalink

Well, as I said this is based on probably out of date info, but most
people will be using kde3 from what I have seen in the irc rooms so it
would appear that it would be opensync 0.2x and whatever version of
kitchensync is in kde3 but do check and make an informed decision. It
will save time and effort for everyone in the long run and increase the
likelihood of the opensuse dev team accepting the rpms for a future
version of the distro and that, again, is better for everyone.

M3PH

-----Original Message-----
From: Adam Williamson [mailto:***@mandriva.com]
Sent: 01 December 2008 21:50
To: Dave Williams
Subject: RE: OpenSUSE SynCE RPM Repository

I tried to do this a while ago (probably a little over a year) but

never

got anywhere as there was too much to learn for me. With learning RPM
and the OBS And finally having to move back to windows for work

reasons - things got a little silly. I'm glad that it has finally been
accomplished but I would question the need for kitchen sync in the

repo

(and granted this is out of date knowledge) because afaik all you need
to do is copy a plugin to the right location. Surely this can be
accomplished without need for another, almost identical, instance of
kitchensync in the OBS that isn't 100% OpenSuSE approved.
The whole ethos of linux is to provide an real alternative to windows.
Having multiple versions of the same program with only finite
differences is really not the way to go. I plead with you to seriously
evaluate the need for a specific kitchensync build And instead go with
some really well written wiki instructions.

I'm not sure of the parameters, here. Exactly what version of
kitchensync is in the official OpenSUSE repos? What opensync build is it
compiled against?

--
adamw

Tejas Guruswamy

2008-12-02 19:30:18 UTC

Permalink

Post by Dave Williams
Well, as I said this is based on probably out of date info, but most
people will be using kde3 from what I have seen in the irc rooms so it
would appear that it would be opensync 0.2x and whatever version of
kitchensync is in kde3 but do check and make an informed decision. It
will save time and effort for everyone in the long run and increase the
likelihood of the opensuse dev team accepting the rpms for a future
version of the distro and that, again, is better for everyone.
M3PH
-----Original Message-----
Sent: 01 December 2008 21:50
To: Dave Williams
Subject: RE: OpenSUSE SynCE RPM Repository
I'm not sure of the parameters, here. Exactly what version of
kitchensync is in the official OpenSUSE repos? What opensync build is it
compiled against?

Don't panic!
What Dave is talking about (I hope) is that the kde3.5.9 (opensync-0.2x)
kitchensync is already included in the openSUSE 11.0 official repos,
which I am well aware of (and I think I mentioned in my message above).
Msynctool 0.22 is also available.
Anyway, openSUSE and the OBS is very flexible. Even if I did decide to
include kitchensync in the SynCE repo, I could simply link the package
to the sources in the official repository, there would be no duplication
of effort.
And don't worry about anyone "rejecting" the packages - it is an ongoing
process, not a final yes/no decision. Even if they aren't included on
the 11.2 DVD, there is no reason why they can't be available on the OSS
repo or as an additional repo on the Build Service as they are now.
The decision as to whether the rpms are going to get integrated into the
official repositories is still a long way off as we are not in time for
the 11.1 release (wasn't aiming to be), meaning we would have to wait
for 11.2 - next year.

What we could use right now is some testers and collaborators on the
project. I made some nice icons for the one-click metapackages which I
will upload to the openSUSE wiki when I update the SynCE page. When that
happens I will also post an announcement on the synce-users list.

Tejas

Dave Williams

2008-12-02 23:58:02 UTC

Permalink

I'm up for that. I'll wipe my vista partition at the weekend.

-----Original Message-----
From: Tejas Guruswamy [mailto:***@gmail.com]
Sent: 02 December 2008 19:30
To: Dave Williams
Cc: synce-devel
Subject: Re: OpenSUSE SynCE RPM Repository

Post by Dave Williams
Well, as I said this is based on probably out of date info, but most
people will be using kde3 from what I have seen in the irc rooms so it
would appear that it would be opensync 0.2x and whatever version of
kitchensync is in kde3 but do check and make an informed decision. It
will save time and effort for everyone in the long run and increase
the likelihood of the opensuse dev team accepting the rpms for a
future version of the distro and that, again, is better for everyone.
M3PH
-----Original Message-----
Sent: 01 December 2008 21:50
To: Dave Williams
Subject: RE: OpenSUSE SynCE RPM Repository
I'm not sure of the parameters, here. Exactly what version of
kitchensync is in the official OpenSUSE repos? What opensync build is
it compiled against?

Dave Williams

2008-12-01 21:48:29 UTC

Permalink

I tried to do this a while ago (probably a little over a year) but never
got anywhere as there was too much to learn for me. With learning RPM
and the OBS And finally having to move back to windows for work related
reasons - things got a little silly. I'm glad that it has finally been
accomplished but I would question the need for kitchen sync in the repo
(and granted this is out of date knowledge) because afaik all you need
to do is copy a plugin to the right location. Surely this can be
accomplished without need for another, almost identical, instance of
kitchensync in the OBS that isn't 100% OpenSuSE approved.

The whole ethos of linux is to provide an real alternative to windows.
Having multiple versions of the same program with only finite
differences is really not the way to go. I plead with you to seriously
evaluate the need for a specific kitchensync build And instead go with
some really well written wiki instructions.

Not spoiling for a fight, honest :)

M3PH

P.s. sorry to adam for sending this mail to him privately. Only noticed
as it was going out ;)

-----Original Message-----
From: Adam Williamson [mailto:***@mandriva.com]
Sent: 27 November 2008 19:45
To: Tejas Guruswamy
Cc: synce-***@lists.sourceforge.net
Subject: Re: OpenSUSE SynCE RPM Repository

Post by Tejas Guruswamy

Post by Adam Williamson
The thing is, KitchenSync is just a front end, like msynctool.

There's

Post by Tejas Guruswamy

Post by Adam Williamson
still, AFAIK, no actual opensync 0.3/0.4 plugin for KDEPIM 4. So if

you

Post by Tejas Guruswamy

Post by Adam Williamson
try to build and use this KitchenSync, you wind up with a setup

which

Post by Tejas Guruswamy

Post by Adam Williamson
cannot actually sync anything with KDE 4, and you're stuck with

opensync

Post by Tejas Guruswamy

Post by Adam Williamson
0.3, which isn't much use in a real world setup.
Presumably it can sync other things using any working opensync 0.3
plugin (heh. heh.), but to me, it doesn't seem worth the effort...

It (kde4-kitchensync) is actually supposed to include the syncing
framework to sync KDE4 PIM data IIRC. I have no idea how complete it

Post by Tejas Guruswamy
though. It now uses akonadi and all kinds of clever fanciness :)

Ah, that I didn't know. I suspect everyone is working away in separate
sealed compartments, here :\. I'll have to test it out.
--
adamw

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/