|
|
| Line 144: |
Line 144: |
| ===Fedora 14 x86-64 Desktop install to VirtualBox (Does not start sweets-distribution)=== | | ===Fedora 14 x86-64 Desktop install to VirtualBox (Does not start sweets-distribution)=== |
| :Emulator and gdm login crash | | :Emulator and gdm login crash |
|
| |
| ==References==
| |
| * http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036464.html
| |
| * http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036465.html
| |
| The general rule for 0.94 and 0.88 repositories is using activities only
| |
| from [Sweets Distribution] packages and only for Fructose. The rest of
| |
| activities need to be handled manually, e.g., installing missed
| |
| dependencies.
| |
| In other words, 0.94 and 0.88 repositories are restricted in case of
| |
| activities (in some meaning it was just a proof of the system).
| |
| Only new system (right now in Factory repository) will cover full cycle
| |
| (activities [itself] will be handled out of native packages, from Sugar
| |
| Network).
| |
| But right now, Factory is not ready for more or less regular usage. So,
| |
| for regular usage choose 0.94 (or 0.88), avoid updating Fructose activities
| |
| from ASLO (excluding only pure python and without dependencies) and use
| |
| them only from [Sweets Distribution] packages.
| |
| I've updated the Wiki:
| |
| http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution#Activities
| |
| *http://wiki.sugarlabs.org/go/Platform_Team/Harmonic_Distribution/1.0/Todo#0.3
| |
|
| |
|
| ==How to Access the Sugar Network when Factory is installed== | | ==How to Access the Sugar Network when Factory is installed== |