Talk:Understanding Sugar code: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
Line 1: Line 1:
==Alternate ways to peel the onion==
==Alternate ways to peel the onion==
I used a non-development image to do this exploration. As a result, I didn't have access to yum, rpm, or a bunch of other value added linux utilities. OLPC does have development images with these utilities added in to make development bearable. A fast way to see the full scope of a sugar installation is this one line command:
I used a standard (non-development) image to do this exploration. As a result, I didn't have access to yum, rpm, or a bunch of other value added linux utilities. OLPC does have development images with these utilities added in to make development bearable. A fast way to see the full scope of a sugar installation is this one line command:


rpm -ql sugar
rpm -ql sugar

Revision as of 14:53, 27 February 2007

Alternate ways to peel the onion

I used a standard (non-development) image to do this exploration. As a result, I didn't have access to yum, rpm, or a bunch of other value added linux utilities. OLPC does have development images with these utilities added in to make development bearable. A fast way to see the full scope of a sugar installation is this one line command:

rpm -ql sugar

It returns all sugar installation files with full paths.