Difference between revisions of "Gentoo"

From Sugar Labs
Jump to navigation Jump to search
m (moved Community/Distributions/Gentoo to Gentoo: restructure)
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Image:Gentoo-logo.svg|65px]]
+
{{Obsolete | Gentoo overlay is not supported any more, [[Platform_Team/Guide/Core_development|sweet build]], a successor, should be used instead}}<br>
  
== Requirements ==
+
{{TOCright}}[[Image:Gentoo-logo.svg|65px]]
  
Overlay demands follow steps
+
== Installation ==
  
* at first, setup overlay in layman
+
At first, setup overlay in layman
  
 
  layman --add sugar
 
  layman --add sugar
  
* if you use stable profiles (x86 and amd64) change your package.keywords
+
To install core sugar components (services, window manager, etc.)
  
  cat <where_your_overlay_is>/profiles/<release>/package.keywords >> /etc/portage/package.keywords
+
  emerge glucose
  
== Installation ==
+
To install core activities
  
NOTE: If you've changed package.use file use "-uDN" flags with follow commands.
+
emerge fructose
  
To install core sugar components (services, window manager, etc.)
+
To install [[0.84/Platform Components|Sugar Platform]]<br>'''NOTE''' In most cases you don't need entirely sugar platform since it's hard to image that Gentoo will be used for regular sugar using, only developing sugar software thus you need only glucose and some parts of fructose like web-activity or terminal-activity.
  
  emerge glucose
+
  emerge sugar-platform
  
To install core activities
+
== Releases ==
  
emerge fructose
+
Overlay was built and run on x86 and amd64(x86_64) platforms.
  
To install non-core activities
+
* '''Stable release'''<br>To install last stable release use ACCEPT_KEYWORDS ''x86'' or ''amd64''
 +
* '''Development release'''<br>To install last release in development cycle use ACCEPT_KEYWORDS ''~x86'' or ''~amd64''
 +
* '''Git release'''<br>Fetch sources from git repositories. All packages have 9999 version numbers.<br>These packages have ''source'' USE flag to install links to .py sources, so you can keep git repositories in your sources directory and all .py files from /usr will be linked to your sources directory. To use this feature you need
 +
** setup SUGAR_SRC_ROOT environment variable
 +
** `git clone` all packages to $SUGAR_SRC_ROOT, names of subdirectories in $SUGAR_SRC_ROOT should be equal to proper package name
 +
** unmask '9999' packages(you can find full list in ''profiles/package.mask'' in overlay directory)
  
  emerge honey
+
''NOTE'' sugar-overlay uses unstable versions for some packages thus if use stable profile, change your package.keywords
 +
  cat <where_your_overlay_is>/profiles/<release>/package.keywords >> /etc/portage/package.keywords
  
 
== Runtime environment ==
 
== Runtime environment ==
Line 37: Line 43:
 
To use jabber connection, configure jabber server in accordance with these [http://wiki.laptop.org/go/Installing_ejabberd/deb instructions].
 
To use jabber connection, configure jabber server in accordance with these [http://wiki.laptop.org/go/Installing_ejabberd/deb instructions].
  
== Packages ==
+
== Bugs ==
 
+
Post overlay related bugs to http://dev.sugarlabs.org/ component ''gentoo-overlay''
Overlay was built and run on x86 and amd64(x86_64) platforms
 
 
 
Sugar packages are being built by [[DeploymentTeam/jhconvert|jhconvert]] and follow its [[DeploymentTeam/jhconvert#Packages|matrix]] of package versions.
 
  
 
== Contacts ==
 
== Contacts ==
Line 50: Line 53:
  
 
* [http://git.overlays.gentoo.org/gitweb/?p=proj/sugar.git Browse overlay]
 
* [http://git.overlays.gentoo.org/gitweb/?p=proj/sugar.git Browse overlay]
* [[DeploymentTeam/jhconvert|Tool to generate Sugar packages]]
+
* [[Deployment Team/jhconvert|Tool to generate Sugar packages]]
  
 
[[Category:Supported systems]]
 
[[Category:Supported systems]]

Latest revision as of 20:42, 1 July 2012

Stop hand.png NOTE:
The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.

Gentoo overlay is not supported any more, sweet build, a successor, should be used instead


Gentoo-logo.svg

Installation

At first, setup overlay in layman

layman --add sugar

To install core sugar components (services, window manager, etc.)

emerge glucose

To install core activities

emerge fructose

To install Sugar Platform
NOTE In most cases you don't need entirely sugar platform since it's hard to image that Gentoo will be used for regular sugar using, only developing sugar software thus you need only glucose and some parts of fructose like web-activity or terminal-activity.

emerge sugar-platform

Releases

Overlay was built and run on x86 and amd64(x86_64) platforms.

  • Stable release
    To install last stable release use ACCEPT_KEYWORDS x86 or amd64
  • Development release
    To install last release in development cycle use ACCEPT_KEYWORDS ~x86 or ~amd64
  • Git release
    Fetch sources from git repositories. All packages have 9999 version numbers.
    These packages have source USE flag to install links to .py sources, so you can keep git repositories in your sources directory and all .py files from /usr will be linked to your sources directory. To use this feature you need
    • setup SUGAR_SRC_ROOT environment variable
    • `git clone` all packages to $SUGAR_SRC_ROOT, names of subdirectories in $SUGAR_SRC_ROOT should be equal to proper package name
    • unmask '9999' packages(you can find full list in profiles/package.mask in overlay directory)

NOTE sugar-overlay uses unstable versions for some packages thus if use stable profile, change your package.keywords

cat <where_your_overlay_is>/profiles/<release>/package.keywords >> /etc/portage/package.keywords

Runtime environment

To use telepathy-salut connection, start avahi

/etc/init.d/avahi-daemon start

To use jabber connection, configure jabber server in accordance with these instructions.

Bugs

Post overlay related bugs to http://dev.sugarlabs.org/ component gentoo-overlay

Contacts

Resources