Changes

mention the need to run "sugar-jhbuild depscheck" regularly more clearly; remove obsolete instructions
Line 37: Line 37:     
''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).
 
''sugar-jhbuild depscheck'' will print a list of required packages. They are part of the distribution you're using and should be installed using your favourite package manager (e.g. aptitude/synaptic for Debian, yum for Fedora).
If you notice that there's a package missing from the depscheck output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].
+
If you notice that there's a package missing from the depscheck output (i.e. it's required for Sugar to work properly and not installed, but depscheck does not mention it), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=Need%20package%20%3cinsert%20name%20of%20package%3e%20on%20%3cinsert%20name%20of%20distribution%3e&description=%3cplease%20explain%20why%20you%20think%20the%20package%20is%20required%20%28e.g.%20error%20message%29%3e file a bug report] (login required first, but currently no automatic redirection to login page) against the sugar-jhbuild Component in the [http://dev.sugarlabs.org/ Sugar Labs bug tracker].
    
Some tips:
 
Some tips:
Line 115: Line 115:  
  ./sugar-jhbuild run
 
  ./sugar-jhbuild run
   −
=== If update and build don't work ===
+
=== If build breaks after an update ===
   −
In May 2008 there were some changes that broke updates on sugar-jhbuild. A version from before this date cannot update or build after this date; the symptoms are various, but generally include errors which mention the "build-scripts" directory. You need to rebuild from scratch in a new jhbuild directory. Something like the following:
+
The packages in sugar-jhbuild are the latest development versions, so you not only get the latest features, but also the latest breakages. The dependencies may change often, too, so be sure to run
 +
./sugar-jhbuild depscheck
 +
regularly and install the missing packages.
   −
cd ..
+
If your problem persists for more than a day (and even though you installed all missing packages), please [http://dev.sugarlabs.org/newticket?component=sugar-jhbuild&version=Git%20as%20of%20bugdate&type=defect&summary=%3cPlease%20enter%20short%20summary%20of%20your%20problem%20here%3e&description=%3cplease%20copy%20exact%20error%20message%20and%20additional%20information%20here%3e file a bug report].
mv sugar-jhbuild sugar-jhbuild.old
  −
git-clone git://dev.laptop.org/sugar-jhbuild
  −
  −
then, to save bandwidth, move the tar files from your old version:
  −
 
  −
mkdir sugar-jhbuild/source
  −
mv sugar-jhbuild.old/source/*.tar* sugar-jhbuild/source
  −
 
  −
then build:
  −
 
  −
cd sugar-jhbuild
  −
./sugar-jhbuild build
  −
 
  −
You may then also see some new dependencies; see the relevant instructions above.  
      
=== From within Sugar ===
 
=== From within Sugar ===
344

edits