687
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: + + + − + Line 14:
Line 17: + + Line 21:
Line 26: − + − + + Line 69:
Line 75: + + Line 87:
Line 95: − : adding -S forces ... wording is not to hand.+ + + Line 97:
Line 107: + + + + + Line 113:
Line 128: + + + + − '''What would an experienced user do next?'''+ − I think it is worth discussing, and I am not sure about this, in this situation (in my experience) many investigatory commands gave misleading answers, I feel because the whole toolbox was not present. Have I drawn the wrong conclusion?+ + +
User:Inkyfingers/Testing Sweets (view source)
Revision as of 03:22, 22 December 2011
, 03:22, 22 December 2011the sweet "base/x11-libs" had a bug that was found in mint
:http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution
:http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution
:works fine for 11.04 Linux Mint 11 I did this and it worked but alsroot wanted me to not put it on the wiki. It installs sweets-sugar 0.94.1 [[User:Satellit]] 9 Dec 2011
:works fine for 11.04 Linux Mint 11 I did this and it worked but alsroot wanted me to not put it on the wiki. It installs sweets-sugar 0.94.1 [[User:Satellit]] 9 Dec 2011
::Link: [[Talk:Platform_Team/Guide/Sugar_via_Sweets#Installing_sweets-sugar_from_Fedora_16_GNOME_3_Terminal|Installing_sweets-sugar_from_Fedora_16_GNOME_3_Terminal]]
:http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Advanced_Topics#Sweets
== Exploring extra documentation ==
== Exploring extra documentation ==
Expanding central section of [[Platform_Team/Guide/Sweets_Usage]]] ...
Expanding central section of [[Platform Team/Guide/Sweets Usage]]] ...
=== Aim of this paper ===
=== Aim of this paper ===
=== Install ===
=== Install ===
Imagine you are now reading [[Sweets/Getting started]]
Imagine you are now reading [[Sweets/Getting started]]
Pre-introductory paragraphs explain what an emulator will look like, and the reasons for experimenting with it.
Introductory paragraph will have "fully" covered distro-non-specific apt-get update.
Introductory paragraph will have "fully" covered distro-non-specific apt-get update.
Then "packagekit" and issues, then download and run script "installer.sh"
Then "packagekit" and issues, then download and run script "installer.sh"
Then, "After installing PackageKit, you need to restart the DBus system bus." or "Relogin from X session"
Then, "After installing PackageKit, you need to restart the DBus system bus," "Relogin from X session," or "Restart the machine"
: Minor issue 1. a) "Restart the machine" seems clumsy. b) distro-non-specific instructions I guess are too difficult. It might be nice to include, say, the best available outside tutorial, even if only to demonstrate good practice?
: Minor issue 1. a) "Restart the machine" seems clumsy. b) I guess distro-non-specific instructions may be too difficult? It might be nice to include, say, the best available outside tutorial, even if only to demonstrate good practice?
''Alternatively, {{Code|sweets}} might be run from the [[Platform_Team/Guide/Sweets_Packaging#Run_Sweets_from_sources|sources]].''
''Alternatively, {{Code|sweets}} might be run from the [[Platform_Team/Guide/Sweets_Packaging#Run_Sweets_from_sources|sources]].''
:Issue 2. This idea needs dealing with at an appropriate level. Is this an alternative for our reader? Under what conditions would the reader start on this method?
:Issue 2. This idea needs dealing with at an appropriate level. Is this an alternative for our reader? Under what conditions would the reader start on this method?
=== Upgrade ===
=== Upgrade ===
Another's '''name''' (alternate usage ''<SWEET>'') is dextrose/sugar.
Another's '''name''' (alternate usage ''<SWEET>'') is dextrose/sugar.
<s>look at : [[Talk:Platform_Team/Guide/Sugar_via_Sweets#Notes_on_how_to_start_0.88_or_0.94| How to start 0.88 or 0.94 Sweets Sugar]]--[[User:Satellit|Satellit]] 15:42, 21 December 2011 (EST). Thanks, added in next paragraph.</s>
: These lines aim to draw attention a perceived difficulty in nomenclature. Improved wording welcome.
: These lines aim to draw attention a perceived difficulty in nomenclature. Improved wording welcome.
sweets -S dextrose/sugar:emulator
sweets -S dextrose/sugar:emulator
To explain,
we add an option, -S ( = --force-suggested) to force, using suggested dependencies
Hopefully one of those commands opened Sugar for you.
Hopefully one of those commands opened Sugar for you.
sweets -S sdk/sugar:emulator
sweets -S sdk/sugar:emulator
we can also add an option to the emulator, for example,
sweets sdk/sugar:emulator -f
will ask the emulator to open, full screen.
'''If you have Sugar running - Explore'''
'''If you have Sugar running - Explore'''
the command {{Code|sweets -R sdk/sugar:emulator}} invoked a massive download of packages - @alsroot what changed?
the command {{Code|sweets -R sdk/sugar:emulator}} invoked a massive download of packages - @alsroot what changed?
: Snip from IRC #sugar-newbies, [21:25] <alsroot> the sweet "base/x11-libs" had a bug that was found in mint
'''What would an experienced user do next?'''
I think it is worth discussing, and I am not sure about this, some investigatory commands gave misleading answers, I feel because the whole toolbox was not present.
Have I drawn the wrong conclusion?
A question regarding -R option. Would the -R option eg:
sweets -R sdk/sugar:emulator
be superfluous straight after {{code|sweets upgrade}}?
I am currently in the above described situation with Sweets on Debian Wheezy. What is suggested here, I will test there.
I am currently in the above described situation with Sweets on Debian Wheezy. What is suggested here, I will test there.