NSLU2-Linux
view · edit · print · history

OpenEmbedded.BitKeeper History

Hide minor edits - Show changes to markup

February 09, 2005, at 09:38 PM by ByronT --
Changed lines 65-70 from:

and all the other cool stuff mentioned at http://www.bitkeeper.com/Hosted.Managing.html

to:

and all the other cool stuff mentioned at http://www.bitkeeper.com/Hosted.Managing.html


BitKeeper and Windows XP

Instructions for getting BitKeeper to run with Windows XP are found http://www.nslu2-linux.org/wiki/OpenEmbedded/BitKeeperXP here. In particular, these instructions are for using the BK Win32 client in conjunction with PuTTy? SSH client.

February 05, 2005, at 07:01 AM by ByronT --
Added lines 11-12:
Warning to dialup users! The download started by the bk clone process is approximately 120MB [as of 2005-02-04].
December 13, 2004, at 10:19 PM by rwhitby --
Changed line 21 from:

This creates the "openembedded" directory below "src".

to:

This creates the "openembedded" directory in "/home/slug".

December 13, 2004, at 10:18 PM by rwhitby --
Changed line 3 from:

You can view our project at http://nslu2-linux.bkbits.net:8080/oe/src?nav=index.html and http://nslu2-linux.bkbits.net:8080/packages/src?nav=index.html

to:

You can view our project at http://nslu2-linux.bkbits.net:8080/openembedded/src?nav=index.html

December 13, 2004, at 10:18 PM by rwhitby --
Changed lines 13-15 from:

First create a directory "src" in your home, i.e.

/home/yourusername/src. Next step into "src"

to:

First create a directory "/home/slug". Next step into "/home/slug"

December 13, 2004, at 10:16 PM by rwhitby --
Changed lines 19-21 from:
 bk clone bk://nslu2-linux.bkbits.net/oe oe
 bk clone bk://nslu2-linux.bkbits.net/packages packages
 bk clone bk://nslu2-linux.bkbits.net/nslu2-package-symlinks nslu2-package-symlinks
to:
 bk clone bk://nslu2-linux.bkbits.net/openembedded openembedded
Changed line 23 from:

This creates the two directories "oe" and "packages" below "src".

to:

This creates the "openembedded" directory below "src".

Changed line 25 from:

To update these directories later (and get the latest changes from the repository) type:

to:

To update this directory later (and get the latest changes from the repository) type:

Changed lines 27-30 from:
 cd oe
 bk pull
 bk -r co -q
 cd ../packages
to:
 cd openembedded
Changed line 49 from:

Contact "rwhitby" or "kergoth" on irc.freenode.net #nslu2-linux and ask them to add your key. Once this has been done, you have to checkout the repository differently, something like this:

to:

Contact "rwhitby", "jacques", "[g2]" or "dyoung" on irc.freenode.net #nslu2-linux and ask them to add your key. Once this has been done, you have to checkout the repository differently, something like this:

Changed lines 51-53 from:
 bk clone bk://nslu2-linux@nslu2-linux.bkbits.net/oe oe
 bk clone bk://nslu2-linux@nslu2-linux.bkbits.net/packages packages
 cd packages
to:
 bk clone bk://nslu2-linux@nslu2-linux.bkbits.net/openembedded openembedded
 cd openembedded
October 29, 2004, at 12:43 AM by ka6sox --
Added line 21:
 bk clone bk://nslu2-linux.bkbits.net/nslu2-package-symlinks nslu2-package-symlinks
October 11, 2004, at 03:28 AM by StE --
Changed lines 19-20 from:
 bk clone bk://nslu2.bkbits.net/oe oe
 bk clone bk://nslu2.bkbits.net/packages packages
to:
 bk clone bk://nslu2-linux.bkbits.net/oe oe
 bk clone bk://nslu2-linux.bkbits.net/packages packages
October 09, 2004, at 04:54 AM by rwhitby --
Changed line 3 from:

You can view our project at http://nslu2.bkbits.net:8080/oe/src?nav=index.html and http://nslu2.bkbits.net:8080/packages/src?nav=index.html

to:

You can view our project at http://nslu2-linux.bkbits.net:8080/oe/src?nav=index.html and http://nslu2-linux.bkbits.net:8080/packages/src?nav=index.html

October 09, 2004, at 04:53 AM by rwhitby --
Changed line 7 from:

If you want to participate, you first have to get your local copy of BitKeeper from http://www.bitkeeper.com/Products.Downloads.html

to:

If you want to participate, you first have to get your local copy of BitKeeper from http://www.bitkeeper.com/Products.Downloads.html

October 09, 2004, at 04:53 AM by rwhitby --
Changed line 64 from:

To be eligible to be considered for manager access to the repositories, you will need to be well-known in the #nslu2-linux IRC channel, and have contributed quite a few changesets. You will also need to have demonstrated expertise in BitKeeper administration.

to:

To be eligible to be considered for manager access to the repositories, you will need to be well-known in the #nslu2-linux IRC channel, and have contributed quite a few changesets. You will also need to have demonstrated expertise in BitKeeper administration. We only need a couple of managers for redundancy reasons, so don't be offended if your request is denied.

October 09, 2004, at 04:51 AM by rwhitby --
Changed line 5 from:

Get ~BitKeeper

to:

Get BitKeeper

October 09, 2004, at 04:51 AM by rwhitby --
Changed lines 3-5 from:

You can view our project at http://nslu2.bkbits.net:8080/oe/src?nav=index.html

Have a look at the metadata tree at http://nslu2.bkbits.net:8080/packages/src?nav=index.html

to:

You can view our project at http://nslu2.bkbits.net:8080/oe/src?nav=index.html and http://nslu2.bkbits.net:8080/packages/src?nav=index.html

Changed line 7 from:

If you want to participate, you first have to get your local copy of ~BitKeeper from http://www.bitkeeper.com/Products.Downloads.html

to:

If you want to participate, you first have to get your local copy of BitKeeper from http://www.bitkeeper.com/Products.Downloads.html

Changed line 11 from:

To get an anonymous checkout of the current development stage, we suggest to do the following things:

to:

To get an anonymous checkout of the current development repositories, we suggest to do the following things:

Changed lines 22-23 from:

_Note: Do not interrupt the download (clone) process or you most likely will have to start over. I have found no way to resume the clone process._

to:

Note: Do not interrupt the download (clone) process or you most likely will have to start over. I have found no way to resume the clone process.

Changed lines 26-49 from:

Now create the environment, using ar`s following script (paste and copy),

and save it under i.e. "set_env"

 export OEPATH=~/src/oe/build-collie:~/src/oe/packages:~/src/oe/oe
 export PATH=$PATH:~/src/oe/oe/bin:/usr/local/arm/2.95.3/bin

 export LD_LIBRARY_PATH=
 export CC=
 export CXX=
 export QMAKESPEC=

 cd ~/src/oe
 PS1?="[oe]$PS1"

_Note: See_ GettingStartedEnvironmentScript _for the latest version of the set_env script._

Now activate it, doing:

 source set_env

To update later:

to:

To update these directories later (and get the latest changes from the repository) type:

Changed lines 36-37 from:

If either of the pull stages fails, and you get errors such as "~ChangeSet? writable but not edited?" or "Entire repository is locked by: RESYNC directory." then you need to fix the RESYNC directory to get around this before trying again:

to:

If either of the pull stages fails, and you get errors such as "ChangeSet writable but not edited?" or "Entire repository is locked by: RESYNC directory." then you need to fix the RESYNC directory to get around this before trying again:

Changed lines 41-45 from:

Now look at :

  bin/oebuild

 and let it run agains the various  *.oe  files, e.g. in:  oe-test.
to:

Developer access

Changed lines 43-54 from:

Note that the oe and the packages project are relatively independent of each other. The packages don't have to live in the oe directory and in fact it would be cleaner to separate them. I.e. in the examples above you may want to say

 cd ../packages 

Instead of

 cd packages.

Developer access

to:

To be eligible to be considered for developer access to the repositories, you should make yourself known on the #nslu2-linux channel on irc.freenode.net and have contributed at least one changeset (ask one of the other developers there to push it for you).

Deleted line 48:
Changed lines 53-54 from:

Then contact "rwhitby" on irc.freenode.net #nslu2-linux and ask him to add your key. Once this has been done, you have to checkout the repository differently, something like this:

to:

Contact "rwhitby" or "kergoth" on irc.freenode.net #nslu2-linux and ask them to add your key. Once this has been done, you have to checkout the repository differently, something like this:

Changed lines 55-57 from:
 bk clone bk://openembedded@openembedded.bkbits.net/oe oe
 cd oe
 bk clone bk://openembedded@openembedded.bkbits.net/packages packages
to:
 bk clone bk://nslu2-linux@nslu2-linux.bkbits.net/oe oe
 bk clone bk://nslu2-linux@nslu2-linux.bkbits.net/packages packages
Deleted line 57:
 cd ..
Added lines 61-70:

Manager access

To be eligible to be considered for manager access to the repositories, you will need to be well-known in the #nslu2-linux IRC channel, and have contributed quite a few changesets. You will also need to have demonstrated expertise in BitKeeper administration.

When you are a manager, you can do

 ssh nslu2-linux.adm@hostme.bkbits.net

and all the other cool stuff mentioned at http://www.bitkeeper.com/Hosted.Managing.html

October 09, 2004, at 04:48 AM by ka6sox --
Changed line 96 from:

Send your key to user "holger" followed by a point, then "schurig" with the domain "gmx" dot "de" (hope the spam sniffers don't get that). Then contact "schurig" on irc.freenode.net #oe and ask him to add your key. Once this has been done, you have to checkout the repository differently, something like this:

to:

Then contact "rwhitby" on irc.freenode.net #nslu2-linux and ask him to add your key. Once this has been done, you have to checkout the repository differently, something like this:

Deleted line 106:
October 09, 2004, at 04:45 AM by ka6sox --
Deleted lines 107-113:

Manager access

When you are a manager, you can do

 ssh openembedded.adm@bkbits.net

and all the other cool stuff mentioned at http://www.bitkeeper.com/Hosted.Managing.html

October 09, 2004, at 04:18 AM by ka6sox --
Changed lines 1-114 from:

Describe BitKeeper here.

to:

View online

You can view our project at http://nslu2.bkbits.net:8080/oe/src?nav=index.html

Have a look at the metadata tree at http://nslu2.bkbits.net:8080/packages/src?nav=index.html

Get ~BitKeeper

If you want to participate, you first have to get your local copy of ~BitKeeper from http://www.bitkeeper.com/Products.Downloads.html

Anonymous checkout

To get an anonymous checkout of the current development stage, we suggest to do the following things:

First create a directory "src" in your home, i.e.

/home/yourusername/src. Next step into "src"

and do the following:

 bk clone bk://nslu2.bkbits.net/oe oe
 bk clone bk://nslu2.bkbits.net/packages packages

_Note: Do not interrupt the download (clone) process or you most likely will have to start over. I have found no way to resume the clone process._

This creates the two directories "oe" and "packages" below "src".

Now create the environment, using ar`s following script (paste and copy),

and save it under i.e. "set_env"

 export OEPATH=~/src/oe/build-collie:~/src/oe/packages:~/src/oe/oe
 export PATH=$PATH:~/src/oe/oe/bin:/usr/local/arm/2.95.3/bin

 export LD_LIBRARY_PATH=
 export CC=
 export CXX=
 export QMAKESPEC=

 cd ~/src/oe
 PS1?="[oe]$PS1"

_Note: See_ GettingStartedEnvironmentScript _for the latest version of the set_env script._

Now activate it, doing:

 source set_env

To update later:

 cd oe
 bk pull
 bk -r co -q
 cd ../packages
 bk pull
 bk -r co -q
 cd ..

If either of the pull stages fails, and you get errors such as "~ChangeSet? writable but not edited?" or "Entire repository is locked by: RESYNC directory." then you need to fix the RESYNC directory to get around this before trying again:

 bk -r check -avf
 bk resolve

Now look at :

  bin/oebuild

 and let it run agains the various  *.oe  files, e.g. in:  oe-test.

Note that the oe and the packages project are relatively independent of each other. The packages don't have to live in the oe directory and in fact it would be cleaner to separate them. I.e. in the examples above you may want to say

 cd ../packages 

Instead of

 cd packages.

Developer access

First, you need to generate an SSH key of type "rsa1":

 ssh-keygen -t rsa1

The key will placed in:

 ~/.ssh/identity.pub

Send your key to user "holger" followed by a point, then "schurig" with the domain "gmx" dot "de" (hope the spam sniffers don't get that). Then contact "schurig" on irc.freenode.net #oe and ask him to add your key. Once this has been done, you have to checkout the repository differently, something like this:

 bk clone bk://openembedded@openembedded.bkbits.net/oe oe
 cd oe
 bk clone bk://openembedded@openembedded.bkbits.net/packages packages
 cd packages
 cd ..
 ... edit ...
 bk citool
 bk push

Manager access

When you are a manager, you can do

 ssh openembedded.adm@bkbits.net

and all the other cool stuff mentioned at http://www.bitkeeper.com/Hosted.Managing.html

view · edit · print · history · Last edited by ka6sox.
Based on work by ka6sox, rwhitby, StE, and ByronT.
Originally by ByronT.
Page last modified on April 14, 2005, at 10:26 PM