Changes

Line 25: Line 25:  
To utilize Services benefits, activity developer just need to [[Activity Team/Documentation/Services/Activity Developers Guide|mention all services(or pure 0install feeds)]] that activity is using. Services infrastructure will provide specified services(and specified versions) for activity and will export environment variables, like LD_LIBRARY_PATH or PYTHONPATH, to activity session, so activity developer shouldn't adapt code to Services.
 
To utilize Services benefits, activity developer just need to [[Activity Team/Documentation/Services/Activity Developers Guide|mention all services(or pure 0install feeds)]] that activity is using. Services infrastructure will provide specified services(and specified versions) for activity and will export environment variables, like LD_LIBRARY_PATH or PYTHONPATH, to activity session, so activity developer shouldn't adapt code to Services.
   −
=== Use non Sugar Platform dependencies ===
+
=== Use non Sugar Platform dependencies in activities ===
    
Sugar Platform could not grow endlessly and components like Qt or OO4Kids will be out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems and do not bundle binaries. See [[Activity_Team/Documentation/Services/Non_Sugar_Platform_Dependencies_Guide|Non Sugar Platform Dependencies Guide]] to know how to use 0install features.
 
Sugar Platform could not grow endlessly and components like Qt or OO4Kids will be out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems and do not bundle binaries. See [[Activity_Team/Documentation/Services/Non_Sugar_Platform_Dependencies_Guide|Non Sugar Platform Dependencies Guide]] to know how to use 0install features.