Michal Hrusecky - 12:28 22.06.09 wrote:
Christopher Stender - 17:01 19.06.09 wrote:
We should definitely use another repository because network:synchronization is IMHO for stuff like rsync or csync and has nothing todo with Mobile/PIM synchronization. What about "Synchronization" as a new toplevel project?
Well, things like rsync already has subproject network:synchronization:files and they are using it for some time already I guess, so moving them somewhere else is out of question. We can create another synchronization repository, but toplevel synchronization directory will be confusing for users searching for rsync and such. I agree, that network:synchronization isn't the best name for this kind of project, although for example opensync can be used to synchronize network stuff as well (Gmail, LDAP, ...) and pilot-link can be used to synchronize your PDA over network too... I would vote for mobile:synchronization too as suggested as it possibly can contain in future other mobile stuff as well - for example ringtone editors, mobile java, maybe even openSUSE Mobile Edition (I guess it would be nice top-level repository for things like Maemo or Moblin, but they already has their own top-level repositories)
darix: Do you think that mobile:synchronization would be too much polluting the namespace?
I spoked with my co-worker and there already some packages which would fit nicely into mobile but wouldn't fit into network:synchronization. For example wammu, gammu which are currently in hardware project or palm-db-tools. Maybe to avoid polution hardware:mobile:{synchronization,utils} doesn't sound bad either... -- Michal Hrusecky Package Maintainer SUSE LINUX, s.r.o e-mail: mhrusecky@suse.cz