184
edits
Changes
Jump to navigation
Jump to search
Line 69:
Line 69: − Sugar loosely depends on the ds-backup-client RPM package, maintained by OLPC and XSCE in two ds-backup repositories. Changes to this dependent package are required by this feature. Coordination with ds-backup developers will be required, to avoid combining incompatible versions of Sugar and ds-backup.+ − OLPC OS and derivatives will be affected, and coordination with their developers required. SoaS, Fedora and Ubuntu systems won't be affected because they do not have ds-backup.+ + + + +
Sugar-server Journal backup (view source)
Revision as of 23:14, 22 April 2016
, 23:14, 22 April 2016no edit summary
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''
This feature is to replace the current ds_backup-client. As an enhancment to the Journal, it is a feature of Sugar. There are parallel feature implementations included in GSOC 16 which may need lead to incompatiblities in the Journal view. These will neeed to be resolved as needed.
The implementation will attempt to preserve compatibility so that it can be retroactively installed on earlier Sugar versions. The documentation will specify how and to which versions this is supported.
The implementation is based on python 2.7. The developers are testing on 13.2.5 and later releases. Implementation assumes future versions of Fedora are compatible. There are no known changes to upstream modules needed at this time.
SOAS, Fedora, and Ubuntu implementations of Sugar are assumed to be compatible. Appropriate testing will be required. Dependencies such as generation of a serial-number can be included in the registration of the server by Sugar.
== Contingency Plan ==
== Contingency Plan ==