> The secondary subject should be "that I will probably never get around
> to" :), but if I do I think it will be shortly after the next release.
>
> Wanted to bounce this around, see what everyone thought. At the moment
> we have 2 libraries that are basically a waste of space without each
> other, libsynce and librapi2, and both of these are pretty pointless
> without a dccm. They also all have to match in versions or things go bad
> fast.
>
> So, I thought once I'd sorted out synce-connector, a hal/udev/manual
> connection replacement for synce-hal, I would combine the two libraries
> and connector into one package, and call it synce-core or even just
> synce.
I completely agree with this. With regards to the name, my preference goes
to synce-core instead of synce. Other suggestion, synce-link.
Guido Diepen
--
Guido Diepen <gu...@jcwodan.nl>
Aviation is proof that given the will, we have the capacity to achieve the
impossible.
--Eddie Rickenbacker
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
