5,705
edits
Changes
Jump to navigation
Jump to search
Line 16:
Line 16: − − == List of services == − − {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" − |-style="background:#787878; color: white;" − ! Service − ! Version − ! Contacts − ! Notes − |- − | saccharin − | 0.0 − | [[User:alsroot]] − | core service − |- − | widgets − | 0.0 − | [[User:alsroot]] − | GUI layer which assimilates various sugar releases changes e.g. let activity developers use new toolbars even in 0.82 environment and do not use many ''ifs'' in code, and provides useful widgets for sugar activity developers − |- − | ... − | − | − | − |- − |}
Platform Team/Package Management System (view source)
Revision as of 08:32, 14 December 2009
, 08:32, 14 December 2009→List of services
Technically, service could be a part of glucose(or some of its releases) but from activity POV it doesn't make much sense, if activity requires some service, saccharin will do nothing if requested service/version is a part of installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case saccharin(via 0install) will just provide proper version to particular activity.
Technically, service could be a part of glucose(or some of its releases) but from activity POV it doesn't make much sense, if activity requires some service, saccharin will do nothing if requested service/version is a part of installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case saccharin(via 0install) will just provide proper version to particular activity.
== Versioning scheme ==
== Versioning scheme ==