Mailinglist Archive: opensuse-mobile (8 mails)
| < Previous | Next > |
Re: [opensuse-mobile] Re: Mobile devices synchronization repository
- From: Christopher Stender <cstender@xxxxxxx>
- Date: Wed, 24 Jun 2009 09:35:27 +0200
- Message-id: <200906240935.32578.cstender@xxxxxxx>
Am Monday 22 June 2009 12:28:15 schrieb Michal Hrusecky:
We can drop the OpenSync toplevel project as soon as we have
mobile:synchronization. So we don't increase the number of toplevel projects.
Okay, I can live with that.
Best regards,
Christopher
--
Christopher Stender, R&D Team Mobile Devices
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
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?
We can drop the OpenSync toplevel project as soon as we have
mobile:synchronization. So we don't increase the number of toplevel projects.
Furthermore, I would like to keep subprojects like:
Synchronization:OpenSync:Factory (devel project for factory)
Synchronization:OpenSync:SVN (svn snapshots)
and maybe for released versions which are still maintained:
Synchronization:OpenSync:$VERSION
What do you think?
I agree that several versions of the same package can be certainly
useful for users. But I would suggest to keep all our packages in same
project to make it easier for users. OpenSync is again great example. If
we split packages under subrepositories then with new PDA I as a user
would need to add SMT:OpenSync repository and
ROOT:Palm/ROOT:WinCE/ROOT:Whatever repository. I would suggest to have
something like ROOT:STABLE for package from last released openSUSE (well
tested package available even for older distributions if possible),
ROOT:FACTORY for factory devel version and ROOT:UNSTABLE for SVN builds,
alpha version testing and such. But this can be probably achieved by
linking/agregating from other subproject if you need/want them anyway.
Okay, I can live with that.
Best regards,
Christopher
--
Christopher Stender, R&D Team Mobile Devices
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
| < Previous | Next > |